From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
To: JFS-Discussion <jfs-discussion@www-124.southbury.usf.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: Testing of filesystems
Date: Tue, 30 Jul 2002 08:22:45 -0400 [thread overview]
Message-ID: <20020730082245.A1590@ti18> (raw)
In-Reply-To: <20020730094902.GA257@prester.freenet.de>; from axel@hh59.org on Tue, Jul 30, 2002 at 11:49:02AM +0200
On Tue, Jul 30, 2002 at 11:49:02AM +0200, Axel Siebenwirth wrote:
> I wonder what a good way is to stress test my JFS filesystem. Is there a tool
> that does something like that maybe? Dont't want performance testing, just
> all kinds of stress testing to see how the filesystem "is" and to check
> integrity and functionality.
See the ext3 cvs tree at
http://sourceforge.net/projects/gkernel
[Jeff Garzik's CVS tree hosts the ext3 tree.]
Andrew Morton, being conscientious and methodical, has written lots of
filesystem testing tools during his work on ext3. Some of these tests
are for specific ext3 regressions, but many are useful as general
integrity tests oriented toward journalled filesystems. He has also
ported/improved several other tools, including a bunch of changes to
the notorious FSX, the File System eXerciser.
The Namesys folks also have a test suite for Reiserfs, see www.namesys.com.
Regards,
Bill Rugolsky
next prev parent reply other threads:[~2002-07-30 12:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 9:49 Testing of filesystems Axel Siebenwirth
2002-07-30 12:07 ` Richard B. Johnson
2002-07-30 12:15 ` Alex Riesen
2002-07-30 15:36 ` Paul Larson
2002-07-30 12:22 ` Bill Rugolsky Jr. [this message]
2002-07-30 12:30 ` Roy Sigurd Karlsbakk
2002-07-30 17:52 ` Cliff White
2002-08-11 2:50 ` Tom Vier
2002-08-11 8:47 ` Hans Reiser
2002-08-11 9:44 ` Andrew Morton
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=20020730082245.A1590@ti18 \
--to=brugolsky@telemetry-investments.com \
--cc=jfs-discussion@www-124.southbury.usf.ibm.com \
--cc=linux-kernel@vger.kernel.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 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.