public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: Chris Wedgwood <cw@f00f.org>
Cc: 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 21:52:51 +0200	[thread overview]
Message-ID: <20050518195251.GY422@unthought.net> (raw)
In-Reply-To: <20050518175925.GA22738@taniwha.stupidest.org>

On Wed, May 18, 2005 at 10:59:25AM -0700, Chris Wedgwood wrote:
> On Wed, May 18, 2005 at 10:38:07AM -0700, Gregory Brauer wrote:
> 
> > May 18 02:59:47 violet kernel: xfs_iget_core: ambiguous vns: vp/0xf53f8ac8, invp/0xe49ccc4c
> 
> I'm pretty sure it's NFS that aggravates this --- can anyone recall
> why?

Not why no - but there where *major* problems with SMP+NFS+XFS up until
2.6.11.

I run 2.6.11(.8/9) on both SMP (dual athlon) and NUMA (64 bit kernel on
dual opteron) with NFS and XFS and haven't yet seen any problems (knock
the wood).

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).

-- 

 / jakob


  reply	other threads:[~2005-05-18 19:53 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 [this message]
2005-05-18 20:00         ` Joshua Baker-LePain
2005-05-18 20:20           ` Jakob Oestergaard
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=20050518195251.GY422@unthought.net \
    --to=jakob@unthought.net \
    --cc=cw@f00f.org \
    --cc=greg@wildbrain.com \
    --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