From: Grzegorz Piotr Jaskiewicz <gj@pointblue.com.pl>
To: Jakob Oestergaard <jakob@unthought.net>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Major XFS problems...
Date: Sat, 11 Sep 2004 13:39:23 +0200 [thread overview]
Message-ID: <4142E3EB.3080308@pointblue.com.pl> (raw)
In-Reply-To: <20040908123524.GZ390@unthought.net>
Jakob Oestergaard wrote:
><frustrated_admin mode="on">
>
>Does anyone actually use XFS for serious file-serving? (yes, I run it
>on my desktop at home and I don't have problems there - such reports are
>not really relevant).
>
>Is anyone actually maintaining/bugfixing XFS? Yes, I know the
>MAINTAINERS file, but I am a little bit confused here - seeing that
>trivial-to-trigger bugs that crash the system and have simple fixes,
>have not been fixed in current mainline kernels.
>
>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?
>
></>
>
>
>
In my expierence XFS, was right after JFS the worst and the slowest
filesystem ever made.
Since than, I am using reiserfs 3.6. I don't need quota for my servers,
but there is patch avaliable for it I belive, from SuSE.
ReiserFS is da most reliable FS for linux (with journaling). If you
don't need journaling, ext2 is da choice.
--
GJ
next prev parent reply other threads:[~2004-09-11 11:39 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
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 [this message]
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=4142E3EB.3080308@pointblue.com.pl \
--to=gj@pointblue.com.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox