From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bodo Eggert <7eggert@gmx.de>
Subject: Re: [RFD] Incremental fsck
Date: Fri, 11 Jan 2008 15:20:33 +0100
Message-ID: <E1JDKkM-0003dY-1b@be1.7eggert.dyndns.org>
References: <9JubJ-5mo-57@gated-at.bofh.it> <9JB3e-85S-13@gated-at.bofh.it> <9JDRm-4bR-1@gated-at.bofh.it> <9JHLl-2dL-1@gated-at.bofh.it>
Reply-To: 7eggert@gmx.de
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
To: Al Boldi <a1426z@gawab.com>, Valerie Henson <val.henson@gmail.com>,
	Rik van Riel <riel@redhat.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Return-path: <linux-kernel-owner+glk-linux-kernel-3=40m.gmane.org-S1761371AbYAKOVo@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

Al Boldi <a1426z@gawab.com> 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!