> 1) Ensure that the file system was properly converted from EXT2 to EXT3
> 
> To convert an EXT2 file system to EXT3, logon as root and run:
> /sbin/tune2fs -j /dev/hdXY
I did that an additional time before just to check, and repeated the 
operation now. Both times I got


# /sbin/tune2fs -j /dev/hda2
tune2fs 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09
The file system already has a journal.

which as far as I understand means the journal was there all along.

> 
> 2) Ensure that the file system is mounted as EXT3
> 
> Check /etc/fstab, and make sure the file system type is ext3
> 
> 3) Ensure that EXT3 is configured to use the journal
> 
> -- PART 1 --
> To verify, look at the output from the command:
> cat /proc/mounts
Now, this is really weird. In /proc/mounts I have 
# grep 'ext[23]' /proc/mounts
/dev/root / ext2 rw 0 0
/dev/hda1 /boot ext3 rw 0 0
/dev/hda5 /usr/work ext3 rw 0 0

while /etc/fstab says

# grep 'ext[23]' /etc/fstab
/dev/hda2 / ext3 defaults 1 1
/dev/hda1 /boot ext3 defaults 1 2
/dev/hda5 /usr/work ext3 defaults 1 2

> 
> -- PART 2 --
[ ... ]

> -- PART 3 --
> If you are transitioning your root file system, you will have to use an
> initrd to boot. Run the mkinitrd program as described in the manual and
> make sure that your LILO or GRUB configuration loads the initrd.
Ahh. That may explain everything. Most of our systems have been set up 
with initrds all along because they are using SCSI disks, but this one did 
not have any. Have now added
        initrd /initrd-2.4.9-31.img
to /boot/grub/grub.conf and run         mkinitrd /boot/initrd-2.4.9-31.img 
2.4.9-31

Now trying a reboot...

Yes, that did the trick. Thanks!

- Toralf


> 
> -----Original Message-----
> From: Toralf Lund [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 08, 2002 6:31 AM
> To: [EMAIL PROTECTED]
> Subject: Why full fsck with ext3?
> 
> 
> On of our hosts will always do a full fsck operation on its root
> filesystem after an unclean shutdown, even though file system type is set
> 
> to "ext3" and the volume has a journal. Any ideas what may be wrong, i.e.
> 
> why it won't recover from the journal instead? --
> Toralf Lund <[EMAIL PROTECTED]>  +47 66 85 51 22
> Kongsberg Scanners AS               +47 66 85 51 00 (switchboard)
> http://www.kscanners.no/~toralf     +47 66 85 51 01 (fax)
> 
> 
> 
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
> 
> 
> 
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
> 



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to