From: Jan-Frode Myklebust <janfrode@parallab.uib.no>
To: Jakob Oestergaard <jakob@unthought.net>, linux-kernel@vger.kernel.org
Subject: Re: Major XFS problems...
Date: Wed, 8 Sep 2004 18:16:52 +0200 [thread overview]
Message-ID: <20040908161652.GA4353@ii.uib.no> (raw)
In-Reply-To: <20040908123524.GZ390@unthought.net>
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
I've shared your frustration this summer:
http://bugzilla.kernel.org/show_bug.cgi?id=2840
http://bugzilla.kernel.org/show_bug.cgi?id=2841
http://bugzilla.kernel.org/show_bug.cgi?id=2929
http://bugzilla.kernel.org/show_bug.cgi?id=3118
but after 2.6.8.1 and going back to 8K stacks, my fileserver has been
stable.
> XFS causes lowmem oom, triggering the OOM killer. Reported by
> as@cohaesio.com on the 18th of august.
Have you tried if this helps:
sysctl -w vm.vfs_cache_pressure=10000
Fixed oom-killer problems for me on 2.6.8-rc2. It was very eager to
kill the backup (tivoli storage manager) client. Haven't needed it so
far on 2.6.8.1.
> A little info on the hardware:
> Big server Small server
> ---------------------- -----------------------
> Intel Xeon Dual Athlon MP
> 7 external SCSI disks 4 internal IDE disks
> IBM hardware RAID Software RAID-1 + LVM
> 600+ GB XFS ~150 GB XFS
> 17+ M files ~1 M files
Dual pentium-III (IBM x330)
2 TB Infortren Eonstore, fibre channel
500 GB in use
~5 M files
Also have another dual Xeon (Dell PowerEdge 2650) with ~1 TB on XFS,
but that's running 2.4.20-30.8.XFS1.3.1smp, and has never had any
problems.
>
> Does anyone actually use XFS for serious file-serving?
Yes,
>
> If XFS is a no-go because of lack of support, is there any realistic
> alternatives under Linux (taking our need for quota into account) ?
>
> And finally, if Linux is simply a no-go for high performance file
> serving, what other suggestions might people have? NetApp?
My impression so far has been more that the 2.6-series might not yet
have been stable enough. Have had to be chasing the leading/bleeding
edge to get away from the known problems. Was looking forward to a
real "maintainer" taking over this series, but that doesn't seem to be
happening..
-jf
next prev parent reply other threads:[~2004-09-08 16:17 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 [this message]
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=20040908161652.GA4353@ii.uib.no \
--to=janfrode@parallab.uib.no \
--cc=jakob@unthought.net \
--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 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.