mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Hans Reiser <reiser@namesys.com>
Cc: Tom Vier <tmv@comcast.net>,
	JFS-Discussion <jfs-discussion@www-124.southbury.usf.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Testing of filesystems
Date: Sun, 11 Aug 2002 02:44:00 -0700	[thread overview]
Message-ID: <3D5631E0.200E37D4@zip.com.au> (raw)
In-Reply-To: <3D562498.9020901@namesys.com>

Hans Reiser wrote:
> 
> Tom Vier wrote:
> 
> >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
> >>
> >>
> ><snip>
> >
> >fsx.c came up a while ago on l-k. it's an old (but still very useful) fs
> >stressor(sp) from neXT. i have a copy davej modded for linux. if you can't
> >find it, i can send it to you. i haven't been brave enough to run it myself,
> >on my alpha's reiserfs. 8) it found some hard to find bugs in ext2 that were
> >lurking for years (iirc).
> >
> >
> >
> It found bugs in reiserfs and we fixed them.:)

fsx-linux is great.  Caused me no end of grief in 2.5.13.  Running
it on small blocksize fs alongside really heavy memory pressure 
touches all sorts of corner cases.

I have a version which is tricked up to understand O_DIRECT
in http://www.zip.com.au/~akpm/linux/ext3-tools.tar.gz

      reply	other threads:[~2002-08-11  9:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30  9:49 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.
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 [this message]

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=3D5631E0.200E37D4@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=jfs-discussion@www-124.southbury.usf.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=tmv@comcast.net \
    /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

all inboxes | Powered by JetHome®