> Andi Kleen wrote: >> Theodore Tso <[EMAIL PROTECTED]> writes: >> > Now, there are good reasons for doing periodic checks every N mounts >> > and after M months. And it has to do with PC class hardware. (Ted's >> > aphorism: "PC class hardware is cr*p"). >> >> If these reasons are good ones (some skepticism here) then the correct >> way to really handle this would be to do regular background scrubbing >> during runtime; ideally with metadata checksums so that you can actually >> detect all corruption. >> >> But since fsck is so slow and disks are so big this whole thing >> is a ticking time bomb now. e.g. it is not uncommon to require tens >> of minutes or even hours of fsck time and some server that reboots >> only every few months will eat that when it happens to reboot. >> This means you get a quite long downtime. > > Has there been some thought about an incremental fsck?
Is that anything like a cluster fsck? ]:> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
