All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Jakob Oestergaard <jakob@unthought.net>
Cc: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Major XFS problems...
Date: Thu, 9 Sep 2004 07:40:47 +1000	[thread overview]
Message-ID: <20040909074046.A3958243@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <20040908123524.GZ390@unthought.net>; from jakob@unthought.net on Wed, Sep 08, 2004 at 02:35:24PM +0200

Hi there,

On Wed, Sep 08, 2004 at 02:35:24PM +0200, Jakob Oestergaard wrote:
> 
> First XFS bug:
> ---------------
> http://oss.sgi.com/bugzilla/show_bug.cgi?id=309
> 
> Submitted in februrary this year - requires server reboot, NFS clients
> will then re-trigger the bug immediately after the NFS server is started
> again.  Clearly not a pleasent problem.
> 
> A fairly simple patch is available, which solves the problem in the most
> common cases.  This simple patch has *not*yet* been included in 2.6.8.1.
> 

Have you asked Christoph if he thinks that patch is ready for
inclusion?  Its possibly just fallen through the cracks.

> Second XFS bug:
> ---------------
> Also causes the 'kernel BUG at fs/xfs/support/debug.c:106' message to be
> printed. This bug is not solved by applying the simple patch to the
> first problem.
> 
> How well known this problem is, I don't know - I can get more details on
> this if anyone is actually interested in working on fixing XFS.

Yes please (it does help to actually contact the maintainers when
reporting bugs...).  It is not well known.

> Third XFS bug:
> --------------
> XFS causes lowmem oom, triggering the OOM killer. Reported by
> as@cohaesio.com on the 18th of august.
> 
> On the 24th of august, William Lee Irwin gives some suggestions and
> mentions  "xfs has some known bad slab behavior."

Hmm?  Which message was that?

> ...
> While the small server seems to be running well now, the large one has
> an average uptime of about one day (!)   Backups will crash it reliably,
> when XFS doesn't OOM the box at random.

It would be a good idea to track the memory statistics while you're
running your workloads to see where in particular the memory is being
used when you hit OOM - /proc/{meminfo,slabinfo,buddyinfo}.  I'd also
be interested to hear if that vfs_cache_pressure tweak that someone
recommended helps your load at all, thanks.

Is this xfsdump you're running for backups?

> Is anyone actually maintaining/bugfixing XFS?

Yes, there's a group of people actively working on it.

> Yes, I know the MAINTAINERS file,

But haven't figured out how to use it yet?

> ...
> trivial-to-trigger bugs that crash the system and have simple fixes,
> have not been fixed in current mainline kernels.

If you have trivial-to-trigger bugs (or other bugs) then please let
the folks at linux-xfs@oss.sgi.com know all the details (test cases,
etc, are quite useful).

cheers.

-- 
Nathan

  parent reply	other threads:[~2004-09-08 21:41 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
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 [this message]
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=20040909074046.A3958243@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=jakob@unthought.net \
    --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 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.