| View previous topic :: View next topic |
| Author |
Message |
kamikaze_gerbil
n00b
Joined: 08 Feb 2003
Posts: 71
Location: Vancouver, Canada
|
 Posted: Sat Mar 27, 2004 9:29 am Post subject: Ext3 booting as Ext2 [Solved] |
 |
|
Had a brown out that caused the computer to reboot and it went into the long prolonged disk checking of ext2. Strange considering I created it as ext3. Looking around I found this:
| Code: | EXT2-fs warning (device ide0(3,3)): ext2_read_super: mounting ext3 filesystem as ext2
|
It does this after all boots. Anyone know why it is mounting as ext2?
Last edited by kamikaze_gerbil on Mon Mar 29, 2004 8:08 am; edited 1 time in total |
|
| Back to top |
|
 |
cylgalad
Veteran
Joined: 18 Apr 2003
Posts: 1327
Location: France
|
| Posted: Sat Mar 27, 2004 10:50 am Post subject: |
|
|
Check your /etc/fstab, the partition might be marked as ext2 instead of ext3.
Also check if you built your kernel with ext3 in it (not as module). |
|
| Back to top |
|
|
kamikaze_gerbil
n00b
Joined: 08 Feb 2003
Posts: 71
Location: Vancouver, Canada
|
| Posted: Sat Mar 27, 2004 10:58 am Post subject: |
|
|
| cylgalad wrote: | Check your /etc/fstab, the partition might be marked as ext2 instead of ext3.
Also check if you built your kernel with ext3 in it (not as module). |
My fstab looks ok
| Code: | | /dev/hda3 / ext3 noatime 0 1 |
ext3 is builtin to the kernel:
| Code: | CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
# CONFIG_EXT3_FS_XATTR_SHARING is not set
# CONFIG_EXT3_FS_XATTR_USER is not set
# CONFIG_EXT3_FS_XATTR_TRUSTED is not set
# CONFIG_EXT3_FS_POSIX_ACL is not set |
Should I enable the extended attributes? Haven't needed to do that before. |
|
| Back to top |
|
|
kamikaze_gerbil
n00b
Joined: 08 Feb 2003
Posts: 71
Location: Vancouver, Canada
|
| Posted: Mon Mar 29, 2004 8:12 am Post subject: |
|
|
OK, finally figured this out. I deleted the sources, keeping the .config file, and re-emerged them. Ran the whole kernel deal and voila, no more mounting as ext2.
There must have been an error somewhere in the sources that was causing the problem.
So, 12 hours and another problem done. On to the next!  |
|
| Back to top |
|
|
|
Kernel & Hardware
