Message-ID: <4554E7C1.1070705@sandeen.net>
Date: Fri, 10 Nov 2006 14:57:37 -0600
From: Eric Sandeen <sandeen@sandeen.net>
User-Agent: Thunderbird 1.5.0.8 (X11/20061107)
MIME-Version: 1.0
To: Steve Grubb <sgrubb@redhat.com>
CC: Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] handle ext3 directory corruption better
References: <200610211129.23216.sgrubb@redhat.com> <20061031095742.GA4241@ucw.cz> <200611011029.39295.sgrubb@redhat.com>
In-Reply-To: <200611011029.39295.sgrubb@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1033
Lines: 23

Steve Grubb wrote:
> On Tuesday 31 October 2006 04:57, Pavel Machek wrote:
>> Nice... can you run the same tool against fsck, too?
> 
> I'll see if I can make that work, too. The fuzzer tries to preserve the bad 
> image so that you can replay the problem for debugging. I think its just a 
> matter of making another copy and using that one instead.

I played with this on xfs a little bit in my spare time, found some
xfs_repair problems.  :)  I'm sure other fs's would have issues as well.

Ideally it would probably be good for the tool to have a "use" mode (try
to use the corrupted fs) and a "check" mode (try to fsck the corrupted fs).

In use   mode, it'd be:  mkfs, fuzz, mount, populate (etc), unmount.
In check mode, it'd be:  mkfs, mount, populate, unmount, fuzz, fsck.

-Eric
-
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/