From: Pavel Machek <pavel@ucw.cz>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] handle ext3 directory corruption better
Date: Tue, 31 Oct 2006 09:57:43 +0000 [thread overview]
Message-ID: <20061031095742.GA4241@ucw.cz> (raw)
In-Reply-To: <200610211129.23216.sgrubb@redhat.com>
Hi!
> The initial image is created in one of 2 ways, either dd a file or mkdir a
> directory depending on what the filesystem creation tools call for. To
> corrupt the image, a version of mangle is used. Mangle is a program that
> corrupts about 10% of the data and favors bytes with a value > 128 to induce
> signed/unsigned problems. The corrupted image is exercised by a program
> called run_test. I separated it from the main program so that you can replay
> a test and debug what is happening.
>
> So, to wrap up...anyone that has anything to do with file system development
> may want to give this tool a try to see how robust any given file system is.
> The program can be grabbed here:
>
> http://people.redhat.com/sgrubb/files/fsfuzzer-0.5.tar.gz
Nice... can you run the same tool against fsck, too?
I did that some time ago, with less evil tool, and got some
interesting results.
(Expectation is that no matter how you corrupt fs, fsck will get it
back to consistent state...)
Pavel
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-10-31 9: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 [this message]
2006-10-31 13:35 ` Phillip Susi
2006-11-01 15:29 ` Steve Grubb
2006-11-10 20:57 ` Eric Sandeen
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=20061031095742.GA4241@ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox