From: Jakob Oestergaard <jakob@unthought.net>
To: Joshua Baker-LePain <jlb17@duke.edu>
Cc: Chris Wedgwood <cw@f00f.org>, Gregory Brauer <greg@wildbrain.com>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: kernel OOPS for XFS in xfs_iget_core (using NFS+SMP+MD)
Date: Wed, 18 May 2005 22:20:14 +0200 [thread overview]
Message-ID: <20050518202014.GZ422@unthought.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0505181556410.6834@chaos.egr.duke.edu>
On Wed, May 18, 2005 at 04:00:08PM -0400, Joshua Baker-LePain wrote:
...
> >
> > Seriously, any 2.6 earlier than .11 is *unusable* for file serving over
> > NFS (at least with XFS which at the moment is the only FS with
> > journalled quota so at least for me that's the only option).
>
> Do you have a test case that would show this up? I've been testing a
> centos-4 based server with the RH-derived 2.6.9-based kernel tweaked to
> disable 4K stacks and enable XFS and haven't run into any issues yet.
> This includes running the parallel IOR benchmark from 10 clients (and
> getting 200MiB/s throughput on reads).
Server must be SMP
Two clients; on each of them untar/cat/delete kernel trees.
You want a few million files on the FS in order to confuse the server
sufficiently for it to screw up severely.
Make sure you keep lots of things going concurrently on the clients.
And don't run as root - common problems are also that files get wrong
ownership/modes (a file created by one unprivileged user shows up as
belonging to another unprivileged user - files can show up with modes
d---------)
I guess RH could have patched up a 2.6.9 to include whatever fixes (more
than one!) for the issues that were resolved from 2.6.9 to 2.6.11.
--
/ jakob
next prev parent reply other threads:[~2005-05-18 20:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 20:45 kernel OOPS for XFS in xfs_iget_core (using NFS+SMP+MD) Gregory Brauer
2005-05-14 18:47 ` Chris Wedgwood
2005-05-18 17:38 ` Gregory Brauer
2005-05-18 17:59 ` Chris Wedgwood
2005-05-18 19:52 ` Jakob Oestergaard
2005-05-18 20:00 ` Joshua Baker-LePain
2005-05-18 20:20 ` Jakob Oestergaard [this message]
2005-05-18 20:53 ` Gregory Brauer
2005-05-18 20:43 ` Gregory Brauer
2005-05-19 19:43 ` Joshua Baker-LePain
2005-05-19 21:00 ` Joshua Baker-LePain
2005-05-19 21:09 ` Lee Revell
2005-05-19 21:16 ` Joshua Baker-LePain
2005-05-19 21:29 ` Steve Lord
2005-05-19 21:32 ` Steve Lord
2005-05-19 21:38 ` Joshua Baker-LePain
2005-05-19 21:43 ` Steve Lord
2005-05-19 21:35 ` Chris Wedgwood
2005-05-19 21:27 ` Chris Wedgwood
2005-05-19 21:42 ` Joshua Baker-LePain
2005-05-19 21:48 ` Joshua Baker-LePain
2005-05-19 22:03 ` Gregory Brauer
2005-08-18 18:49 ` kristina clair
2005-08-18 22:58 ` Nathan Scott
2005-08-19 14:59 ` kristina clair
2005-05-19 21:49 ` Lee Revell
2005-05-19 21:52 ` Joshua Baker-LePain
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=20050518202014.GZ422@unthought.net \
--to=jakob@unthought.net \
--cc=cw@f00f.org \
--cc=greg@wildbrain.com \
--cc=jlb17@duke.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox