I understand what you're saying. I wonder if perhaps, though, the disconnect between your statements and that of Brandon's is the fact that this isn't a standard "crash". This is a situation in which the drives just go "POOF". Not something common, but certainly not unheard of.
In that situation the journal will be useful if not only during the ensuing fsck. When the drives disappear it really doesn't matter if the journal is out of sync. Recovery will only happen during the next reboot when the compute is able to attach to the storage backend on which all of the VM's disks reside. -Mathew "When you do things right, people won't be sure you've done anything at all." - God; Futurama "We'll get along much better once you accept that you're wrong and neither am I." - Me On Wed, Oct 30, 2013 at 2:58 PM, Edward Ned Harvey (lopser) < lop...@nedharvey.com> wrote: > Journaling is designed explicitly for the purpose of eliminating the need > for fsck after system crash. > > Whether checking is done per-inode on the fly, or once at filesystem mount > based on a rotating buffer, is an implementation detail. It doesn't change > the fact that fsck after crash is unnecessary. > > Journaling does not completely eliminate the need for fsck in all > circumstances - that's what end-to-end data integrity is for, as > implemented in zfs and btrfs and friends. But journaling and > end-to-end-data-integrity alike, both at least eliminate the need for fsck > after crash. > > But don't take my word for it. I'm a stranger on the internet repeating > something I read somewhere. Take it from these other strangers instead, > who at least cite their references, which may no longer exist: > http://en.wikipedia.org/wiki/Journaling_file_system > > _______________________________________________ > Tech mailing list > Tech@lists.lopsa.org > https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech > This list provided by the League of Professional System Administrators > http://lopsa.org/ >
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
