public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: Anando Bhattacharya <a3217055@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Major XFS problems...
Date: Wed, 8 Sep 2004 19:30:37 +0200	[thread overview]
Message-ID: <20040908173037.GI390@unthought.net> (raw)
In-Reply-To: <1094661418.19981.36.camel@hole.melbourne.sgi.com>

On Thu, Sep 09, 2004 at 02:36:58AM +1000, Greg Banks wrote:
> On Thu, 2004-09-09 at 01:44, Jakob Oestergaard wrote:
> > SMP systems on 2.6 have a problem with XFS+NFS.
> 
> Knfsd threads in 2.6 are no longer serialised by the BKL, and the
> change has exposed a number of SMP issues in the dcache.  Try the
> two patches at
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=108330112505555&w=2
> 
> and
> 
> http://linus.bkbits.net:8080/linux-2.5/cset@1.1722.48.23
> 
> (the latter is in recent Linus kernels).  If you're still having
> problems after applying those patches, Nathan and I need to know.
> 

Ok - Anders (as@cohaesio.com) will hopefully get a test setup (similar
to the big server) running tomorrow, and will then see if the system can
be broken with these two patches applied.

Are we right in assuming that no other patches should be necessary atop
of 2.6.8.1 in order to get a stable XFS?   (that we should not apply
other XFS specific patches?)

Thanks,

-- 

 / jakob


  reply	other threads:[~2004-09-08 17:31 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08 12:35 Major XFS problems Jakob Oestergaard
2004-09-08 15:04 ` Anando Bhattacharya
2004-09-08 15:44   ` Jakob Oestergaard
2004-09-08 16:36     ` Greg Banks
2004-09-08 17:30       ` Jakob Oestergaard [this message]
2004-09-09  2:42         ` Greg Banks
2004-09-08 19:06       ` Bill Davidsen
2004-09-09  3:23         ` Greg Banks
2004-09-09 14:00       ` Jakob Oestergaard
2004-09-10  2:40         ` Greg Banks
2004-09-10  3:04           ` Kyle Moffett
2004-09-10  3:24             ` Greg Banks
2004-09-13  7:29         ` Jakob Oestergaard
2004-09-17 11:26           ` [PATCH] " Jakob Oestergaard
2004-09-29 21:45             ` Christoph Hellwig
2004-09-29 22:16               ` Linus Torvalds
2004-09-08 16:16 ` Jan-Frode Myklebust
2004-09-08 21:40 ` Nathan Scott
2004-09-08 23:22   ` Jakob Oestergaard
2004-09-08 23:42     ` Nathan Scott
2004-09-09 12:11       ` Jakob Oestergaard
2004-09-09 18:09         ` Chris Wedgwood
2004-09-11 11:39 ` Grzegorz Piotr Jaskiewicz
2004-09-11 13:03   ` Bjoern Brauel
2004-09-11 13:38   ` Anton Blanchard
2004-09-11 14:54     ` Miquel van Smoorenburg
2004-09-11 18:20     ` Grzegorz Piotr Jaskiewicz
2004-09-11 13:58 ` Clemens Schwaighofer
  -- strict thread matches above, loose matches on Subject: below --
2004-09-08 13:07 Piszcz, Justin Michael
2004-09-08 13:26 ` Jakob Oestergaard
2004-09-08 15:24 Piszcz, Justin Michael
     [not found] <20040908133954.GB390@unthought.net>
     [not found] ` <20040909074533.B3958243@wobbly.melbourne.sgi.com>
     [not found]   ` <413F823F.3020507@xfs.org>
2004-09-09  6:52     ` Dave Chinner
2004-09-09  8:10       ` Andrew Morton
     [not found] <2Ca3I-2kY-7@gated-at.bofh.it>
     [not found] ` <2Cdl9-4Pc-65@gated-at.bofh.it>
2004-09-11  9:21   ` ADH

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=20040908173037.GI390@unthought.net \
    --to=jakob@unthought.net \
    --cc=a3217055@gmail.com \
    --cc=gnb@melbourne.sgi.com \
    --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