New concept of ext3 disk checks

[Otto Wyss]

I've just read about "Increasing ext3 Disk Checks In The Event Of
Improper Shutdown" in Kernel-Traffic. Since in theory journalling file
systems may prevent any disk corruption the disk checks from the ext2
area doesn't make much sense anymore. Also more and more system don't
boot regularly anymore so the time frame between check isn't
predictable. To take into account that the practice not always behaves
as the theory says, I suggest another concept for ext3 disk checks:

- Instead of checks forced during startup checks are done during runtime
(at low priority). It has to be determined if these checks are _only_
checks or if they also include possible fixes. Possible solution might
distinct between the severity of any discovered problem.

The advantage of such a concept are rather obvious, desktop systems
don't have to use ridiculous high check interval values or disable
checks altogether and server systems may run forever. Also checks may be
done first on the written disk sectors. On an average loaded system,
this way malfunctioning software are detected within minutes and
hardware possibly within days, a rather high improvement to the current
detection time of sometimes months.

O. Wyss

-- 
See a huge pile of work at "http://wyodesktop.sourceforge.net/";
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/