From: Hans Reiser <reiser@namesys.com>
To: Dave Jones <davej@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
reiserfs-dev@namesys.com, Nikita Danilov <god@namesys.com>,
green@thebsh.namesys.com
Subject: Re: [reiserfs-dev] fsx for Linux showing up reiserfs problem?
Date: Sat, 15 Dec 2001 20:08:01 +0300 [thread overview]
Message-ID: <3C1B8371.7050008@namesys.com> (raw)
In-Reply-To: <20011215154029.A3954@suse.de>
Dave Jones wrote:
>Hi folks,
> After reading the article at http://www.kerneltrap.com/article.php?sid=415&mode=thread&order=0
>on the FreeBSD guys finding a bunch of NFS bugs with a stress tool,
>I took a look at fsx and played with it a little under Linux..
>
>The changes to make it work are trivial, and are at
>http://www.codemonkey.org.uk/cruft/fsx-linux.c
>(non-existant include & expected mmap() behaviour differences)
>
>I've done a few tests on local filesystems, and so far Ext2 & Ext3
>seem to be holding up..
>
>Reiserfs however dies very early into the test..
>
> truncating to largest ever: 0x3f15f
> READ BAD DATA: offset = 0x1d3d4, size = 0x962f
> OFFSET GOOD BAD RANGE
> 0x1d3d4 0x177d 0x0000 0x 563
> operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
>
>Options used were ./fsx -c1234 /mnt/test/testfile
>(Although it seems to crash with any -c option)
>
>Looks like an interesting tool, and probably something that should
>be added to testsuites like Cerberus.
>
>regards,
>Dave.
>
Thanks Dave, Elena and Nikita and Green, take a look at this.
Hans
prev parent reply other threads:[~2001-12-15 17:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-15 15:40 fsx for Linux showing up reiserfs problem? Dave Jones
2001-12-15 16:18 ` Martin Josefsson
2001-12-15 16:52 ` More fun with fsx Dave Jones
2001-12-16 14:53 ` Trond Myklebust
2001-12-16 14:58 ` Dave Jones
2001-12-16 15:26 ` Dave Jones
2001-12-16 15:39 ` Trond Myklebust
2001-12-16 15:47 ` Dave Jones
2001-12-16 15:50 ` Trond Myklebust
2001-12-16 18:48 ` Trond Myklebust
2001-12-16 20:59 ` Dave Jones
2001-12-16 21:19 ` Trond Myklebust
2001-12-16 21:34 ` Dave Jones
2001-12-17 0:00 ` Trond Myklebust
[not found] ` <Pine.LNX.4.33.0112170116160.29678-100000@Appserv.suse.de>
2001-12-17 1:33 ` Trond Myklebust
2001-12-17 1:37 ` Dave Jones
2001-12-17 1:47 ` Trond Myklebust
2001-12-17 1:50 ` Dave Jones
2001-12-17 2:51 ` Dave Jones
2001-12-17 9:59 ` Trond Myklebust
2001-12-17 14:30 ` Dave Jones
2001-12-17 14:41 ` Dave Jones
2001-12-17 16:06 ` Trond Myklebust
2001-12-17 16:15 ` Dave Jones
2001-12-18 20:31 ` David S. Miller
2001-12-18 20:36 ` Dave Jones
2001-12-20 15:55 ` Nathan Straz
2001-12-20 16:02 ` Dave Jones
2001-12-15 17:08 ` Hans Reiser [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=3C1B8371.7050008@namesys.com \
--to=reiser@namesys.com \
--cc=davej@suse.de \
--cc=god@namesys.com \
--cc=green@thebsh.namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@namesys.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.