From: Jakob Oestergaard <jakob@unthought.net>
To: Nathan Scott <nathans@sgi.com>
Cc: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Major XFS problems...
Date: Thu, 9 Sep 2004 01:22:11 +0200 [thread overview]
Message-ID: <20040908232210.GL390@unthought.net> (raw)
In-Reply-To: <20040909074046.A3958243@wobbly.melbourne.sgi.com>
On Thu, Sep 09, 2004 at 07:40:47AM +1000, Nathan Scott wrote:
> Hi there,
>
...
> >
> > 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.
With the feedback I've seen thus far, it seems that one possible
explanation for this is, that the patch only papers over the problem (by
changing XFS), but that the real problem is not in XFS and thus might be
fixed for real by a completely different set of patches (which sort of
makes sense since the small patch only cures the problem in the common
cases).
We'll know more about this tomorrow, hopefully, if Anders gets the new
test system up and running.
> > 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?
http://lkml.org/lkml/2004/8/24/140
>
> > ...
> > 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}.
Slab usage in kilo-kilo-bytes (one K on the graph is one Megabyte):
http://saaby.com/slabused.gif
This was presented earlier in
http://lkml.org/lkml/2004/8/24/53
> I'd also
> be interested to hear if that vfs_cache_pressure tweak that someone
> recommended helps your load at all, thanks.
Anders will hopefully get a lot of this testing done tomorrow - by then
hopefully we'll know a lot more about all this.
>
> Is this xfsdump you're running for backups?
Veritas BackupExec was used, as far as I know
xfsdump will be tested soon.
The "small server" is backed up with tar (by Amanda).
>
> > 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?
Read on ;)
>
> > ...
> > 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).
They've known for 7 months (bug 309 in your bugzilla), but the problem
is still trivially triggered in 2.6.8.1.
That's why I posted to LKML.
We got a lot of very useful feedback from a broad audience, and it seems
that it *might* turn out that this XFS problem was never really a
problem in XFS itself.
Let's see what tomorrow brings.
Thaks all!
--
/ jakob
next prev parent reply other threads:[~2004-09-08 23:22 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
2004-09-08 23:22 ` Jakob Oestergaard [this message]
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=20040908232210.GL390@unthought.net \
--to=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@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