From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Boldi Subject: Re: [RFD] Incremental fsck Date: Sat, 12 Jan 2008 13:20:53 +0300 Message-ID: <200801121320.53882.a1426z@gawab.com> References: <9JubJ-5mo-57@gated-at.bofh.it> <9JHLl-2dL-1@gated-at.bofh.it> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: 7eggert@gmx.de Return-path: Received: from [212.12.190.41] ([212.12.190.41]:33714 "EHLO raad.intranet" rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1752379AbYALKVn (ORCPT ); Sat, 12 Jan 2008 05:21:43 -0500 In-Reply-To: Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Bodo Eggert wrote: > Al Boldi wrote: > > Even after a black-out shutdown, the corruption is pretty minimal, using > > ext3fs at least. So let's take advantage of this fact and do an > > optimistic fsck, to assure integrity per-dir, and assume no external > > corruption. Then we release this checked dir to the wild (optionally > > ro), and check the next. Once we find external inconsistencies we either > > fix it unconditionally, based on some preconfigured actions, or present > > the user with options. > > Maybe we can know the changes that need to be done in order to fix the > filesystem. Let's record this information in - eh - let's call it a > journal! Don't mistake data=journal as an fsck replacement. Thanks! -- Al