On Thu, Feb 12, 2009 at 8:13 PM, Stefan Monnier <monnier@iro.umontreal.ca> wrote: >>> filesystem... so considering its size, I'd turn it off. Hopefully the >>> "fsck takes _forever_" problem will die when btrfs becomes the >>> standard filesystem. > >> Just a reminder: Linux has xfs since 2002. A full-blown fsck on xfs is >> a rare thing. > > Similarly, I don't know of any case where fsck on an ext3 partition > turned out to be useful. As a matter of fact, my home router's ext3 > partition is never fsck'd (it would take way too much time to this poor > 266MHz thingy to fsck my 1TB filesystem). I've seen plenty of cases that fsck has made a filesystem consistent again, but like Bryn says, there's only so much it can do. from e2fsck(8): e2fsck is used to check a Linux second extended file system (ext2fs). E2fsck also supports ext2 filesystems containing a journal, which are also sometimes known as ext3 filesystems, by first applying the journal to the filesystem before continuing with normal e2fsck processing. After the journal has been applied, a filesystem will normally be marked as clean. Hence, for ext3 filesystems, e2fsck will normally run the journal and exit, unless its superblock indicates that further checking is required. So the fsck that is done at boot time only replays the journal if a filesystem wasn't unmounted cleanly. Its only when after replaying the journal that if further checking is required a full fsck (the one that takes forever) is needed. If a full fsck is needed you'll be dropped to emergency mode (or something) where you need to enter your root password and run the full fsck (at least that's how it works in RHEL and Fedora). --Dave _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
