From: Theodore Tso <tytso@mit.edu>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reiserFS?
Date: Sun, 16 Jul 2006 14:14:31 -0400 [thread overview]
Message-ID: <20060716181431.GA27306@thunk.org> (raw)
In-Reply-To: <20060716174636.GA3615@gallifrey>
On Sun, Jul 16, 2006 at 06:46:37PM +0100, Dr. David Alan Gilbert wrote:
> That leads me to ask what level of testing is performed on each
> filesystem - are there filesystem torture tests that are getting
> run by someone (who?) on various filesystems (preferably on large
> TB sized ones, preferably with simulated failures and resets)?
> The discussions on Ext4 a few weeks ago made me think that the
> thing I'd value more than anything else would be a damn good
> test regime.
As far as I know ext2/3 is the only filesystem with a fsck tool that
has a regression test suite. It's always amazed me that filesystem
consistency checkers and repair tools get so little attenion by most
filesystem developers.
As far as random torture testing, Pavel has written a random test tool
that punches random errors into random blocks of a filesystem, and
that was used to uncover a couple of cases that e2fsprogs didn't
handle cleanly. Those were reported to me, and I fixed them, and the
edge cases were encorprated into the regression test suite.
IIRC it came up in discussion a few weeks ago one LKML or
linux-fsdevel (I can't remember which), and I believe either someone
from XFS or Reiser team was going to take Pavel's torture tester and
adapt it do some robustifying of their filesystem's repair
capabilities.
Finally, the good folks at the Stanford Metacompilation group did some
very interesting work to find bugs in three common Linux filesystems:
http://keeda.stanford.edu/~junfeng/papers/osdi04/osdi04.html
Regards,
- Ted
next prev parent reply other threads:[~2006-07-16 18:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-16 16:16 reiserFS? Xavier Roche
2006-07-16 16:28 ` reiserFS? Christian Trefzer
2006-07-16 16:56 ` reiserFS? Theodore Tso
2006-07-16 17:26 ` reiserFS? Lexington Luthor
2006-07-16 17:48 ` reiserFS? Theodore Tso
2006-07-16 20:01 ` "Why Reuser 4 still is not in" doc (was: 'reiserFS?') Diego Calleja
2006-07-16 21:11 ` "Why Reuser 4 still is not in" doc Lexington Luthor
2006-07-16 21:28 ` Joshua Hudson
2006-07-16 22:53 ` Lexington Luthor
2006-07-17 9:42 ` Jan Engelhardt
2006-07-17 16:38 ` Lexington Luthor
2006-07-20 6:52 ` Tilman Schmidt
2006-07-16 17:46 ` reiserFS? Dr. David Alan Gilbert
2006-07-16 18:14 ` Theodore Tso [this message]
2006-07-17 15:01 ` reiserFS? Matthias Andree
2006-07-17 21:07 ` reiserFS? Helge Hafting
-- strict thread matches above, loose matches on Subject: below --
2006-07-16 12:45 reiserFS? ivo welch
2006-07-16 13:50 ` reiserFS? Matthias Andree
2006-07-16 15:29 ` reiserFS? Lexington Luthor
2006-07-16 16:55 ` reiserFS? grundig
2006-07-17 9:23 ` reiserFS? Arjan van de Ven
2006-07-17 16:32 ` reiserFS? Lexington Luthor
2006-07-17 14:56 ` reiserFS? Matthias Andree
2006-07-16 14:19 ` reiserFS? Joseph Le-Phan
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=20060716181431.GA27306@thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
/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