From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-list] Re: Apparent instability of reiserfs on 2.4.1
Date: 11 Feb 2001 20:56:16 +0100 [thread overview]
Message-ID: <oupvgqhkn8f.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <E14S01O-0004Su-00@the-village.bc.nu>
In-Reply-To: Alan Cox's message of "11 Feb 2001 18:13:47 +0100"
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > LADDIS is the industry standard benchmark for NFS. It crashes for ReiserFS and
> > NFS. We can't afford to buy it, as it is proprietary software. Once Nikita has
> > finished testing his changes, we will ask someone to test it for us though.
> >
>
> Do you know if the connectathon test suites show the problem?
The reiserfs nfs problem in standard 2.4 is very simple -- it'll barf as soon
as you run out of file handle/inode cache. Any workload that accesses
enough files in parallel can trigger it.
Fixes do exist, but require bigger changes in nfsd. Basically you need to
hand out an 64bit inode in the nfs filehandle, and pass the upper 32bits
to the low level file system for efficient lookup (actually is all not
too difficult to implement, just requires very uncodefreezefriendly changes
to nfsd)
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-11 19:56 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 12:06 Apparent instability of reiserfs on 2.4.1 Hans Reiser
2001-02-07 15:47 ` Chris Mason
2001-02-07 16:38 ` [reiserfs-list] " David Rees
2001-02-07 16:48 ` Chris Mason
2001-02-08 6:34 ` Daniel Stone
2001-02-10 13:02 ` Chris Wedgwood
2001-02-10 13:05 ` Daniel Stone
2001-02-10 13:08 ` Chris Wedgwood
2001-02-11 7:00 ` Hans Reiser
2001-02-12 0:56 ` Chris Mason
2001-02-12 19:11 ` Marcelo Tosatti
2001-02-12 20:42 ` Hans Reiser
2001-02-12 19:33 ` Marcelo Tosatti
2001-02-12 21:01 ` Hans Reiser
2001-02-12 23:03 ` Chris Mason
2001-02-12 22:39 ` Hans Reiser
2001-02-13 0:18 ` Chris Mason
2001-02-12 22:44 ` Hans Reiser
2001-02-11 6:58 ` Hans Reiser
2001-02-10 14:47 ` Alan Cox
2001-02-10 21:16 ` David Ford
2001-02-11 0:36 ` Andrius Adomaitis
2001-02-11 8:29 ` Hans Reiser
[not found] ` <wvu261oa80.fsf@freeze.oslo.dnmi.no>
2001-02-11 8:59 ` Hans Reiser
2001-02-11 9:52 ` Adrian Phillips
2001-02-11 9:47 ` Hans Reiser
2001-02-11 17:10 ` Alan Cox
2001-02-11 19:56 ` Andi Kleen [this message]
2001-02-12 2:17 ` Rogerio Brito
2001-02-12 9:49 ` Andi Kleen
2001-02-12 13:39 ` Henning P. Schmiedehausen
2001-02-11 21:16 ` Hans Reiser
2001-02-12 9:36 ` Alan Cox
2001-02-11 10:53 ` Alan Cox
2001-02-11 8:50 ` Hans Reiser
[not found] ` <3A818619.7C3967BC@baldauf.org>
2001-02-07 17:39 ` Chris Mason
2001-02-07 17:53 ` Xuan Baldauf
2001-02-07 19:14 ` Xuan Baldauf
2001-02-07 21:47 ` Chris Wedgwood
2001-02-07 21:55 ` Chris Mason
2001-02-07 22:05 ` Xuan Baldauf
2001-02-07 22:13 ` Chris Mason
2001-02-07 18:41 ` Vedran Rodic
2001-02-07 18:45 ` Chris Mason
2001-02-07 19:15 ` Ivan Pulleyn
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=oupvgqhkn8f.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox