Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763196AbYALKVx (ORCPT ); Sat, 12 Jan 2008 05:21:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758689AbYALKVo (ORCPT ); Sat, 12 Jan 2008 05:21:44 -0500 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 From: Al Boldi To: 7eggert@gmx.de Subject: Re: [RFD] Incremental fsck Date: Sat, 12 Jan 2008 13:20:53 +0300 User-Agent: KMail/1.5 References: <9JubJ-5mo-57@gated-at.bofh.it> <9JHLl-2dL-1@gated-at.bofh.it> In-Reply-To: Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200801121320.53882.a1426z@gawab.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1000 Lines: 27 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/