On Sun, 3 Aug 2003, Luca Olivetti wrote: > Buchan Milne wrote: > > > hangs just after resuming). An fsck gets forced on the rootfs (whereas it > > should just replay the journal), and then you see: > > Isn't this the job of the corresponding fsck? At least this is true for xfs:
Yes, but as the subject says, this is with ext3, which happens to be the default filesystem, so by default newbies see this ... The last time I tested ReiserFS as root fs (which was a while ago) it was pretty robust, and repeated hard reboots couldn't do a thing to it, where with XFS as root fs (last time I tried this was 9.0) it would easily destroy a file that was open, most commonly seen by having a few files required by xdm removed ... Anyway, with ext3, I guess the complication is that fsck.ext2 and fsck.ext3 are the same file, and ext2 should be doing an fsck on boot. But, this discussion should be done in the bugzilla entry, so can someone confirm if this still happens on cooker (otherwise I will do it tomorrow morning, I think I still have ext3 on / on my cooker box). Regards, Buchan -- |----------------Registered Linux User #182071-----------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 ****************************************************************** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. ******************************************************************
