In <20000117205037.A25108@pcep-jamie.cern.ch> Jamie Lokier (lkd@tantalophile.demon.co.uk) wrote:
JL> Khimenko Victor wrote:
>> 1. System crashed due software or hardware error while sutting down so
>> it's marked clean but not superblocks are Ok.
>> 2. There are some nasty error in ext2fs kernel code (or even more subtle
>> bug in non-ext2fs kernel code: usually bug in kernel will oops and/or lock
>> kernel and it should be REALLY weird bug to not crash kernel but force it
>> to write wrong superblocks on disk).
>>
>> If you are not playing with development kernels both have near zero
>> probability.
JL> I _am_ playing with development kernels.
JL> I have to reboot so often, and that's why I want the mount to not take
JL> any time :-)
Then you should expect loss of data :-) In fact data loss caused by
big-filesystem-code-rework for 2.3 last summer was NOT detected by this check
(I'm not sure if something EVER was detected by that check, but who knows?).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:17 EST