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 [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
