From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Boldi Subject: [RFD] Incremental fsck Date: Wed, 9 Jan 2008 00:22:55 +0300 Message-ID: <200801090022.55589.a1426z@gawab.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org To: linux-fsdevel@vger.kernel.org Return-path: Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Andi Kleen wrote: > Theodore Tso 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? You know, somehow fencing a sub-dir to do an online fsck? Thanks for some thoughts! -- Al