Paul Wouters wrote: > Just to remind you, what people have a problem with is not running manual > fsck's on certain filesystems. People have a problem with machines being stuck > in single user mode waiting for manual intervention leading "fsck -y" anyway > on the root filesystem. > > If my remote machine comes back, starts sshd, and then has /home not mounted > because of an INCOSISTENCT FILESYSTEM error, I'm more then happy to run fsck -y > manually. As a bit of a tangent, if you see this fairly often, any idea why? Journaling should in general protect you from needing any sort of fsck after a power loss or oops; that's what they're for, right. I'd be curious to know what sorts of corruptions you wind up finding. How the corruption gets coped with once found is one point worth discussing, but where's it coming from in the first place? My guess is it's lack of barrier writes, but it's worth getting to the bottom of it, and hopefully this will make the choice of e2fsck parameters less relevant. :) -Eric -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
