From: Eric Sandeen <sandeen@sandeen.net>
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
Date: Fri, 10 Nov 2006 14:57:37 -0600 [thread overview]
Message-ID: <4554E7C1.1070705@sandeen.net> (raw)
In-Reply-To: <200611011029.39295.sgrubb@redhat.com>
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
next prev parent reply other threads:[~2006-11-10 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 15:29 [PATCH] handle ext3 directory corruption better Steve Grubb
2006-10-31 9:57 ` Pavel Machek
2006-10-31 13:35 ` Phillip Susi
2006-11-01 15:29 ` Steve Grubb
2006-11-10 20:57 ` Eric Sandeen [this message]
2006-11-12 13:39 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-10-20 19:17 Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4554E7C1.1070705@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sgrubb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.