From: Al Boldi <a1426z@gawab.com>
To: linux-raid@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Large single raid and XFS or two small ones and EXT3?
Date: Fri, 23 Jun 2006 17:01:44 +0300 [thread overview]
Message-ID: <200606231701.44803.a1426z@gawab.com> (raw)
In-Reply-To: <449BE381.6070000@cjx.com>
Chris Allen wrote:
> Francois Barre wrote:
> > 2006/6/23, PFC <lists@peufeu.com>:
> >> - XFS is faster and fragments less, but make sure you have a
> >> good UPS
> >
> > Why a good UPS ? XFS has a good strong journal, I never had an issue
> > with it yet... And believe me, I did have some dirty things happening
> > here...
> >
> >> - ReiserFS 3.6 is mature and fast, too, you might consider it
> >> - ext3 is slow if you have many files in one directory, but
> >> has more
> >> mature tools (resize, recovery etc)
> >
> > XFS tools are kind of mature also. Online grow, dump, ...
> >
> >> I'd go with XFS or Reiser.
> >
> > I'd go with XFS. But I may be kind of fanatic...
>
> Strange that whatever the filesystem you get equal numbers of people
> saying that they have never lost a single byte to those who have had
> horrible corruption and would never touch it again. We stopped using XFS
> about a year ago because we were getting kernel stack space panics under
> heavy load over NFS. It looks like the time has come to give it another
> try.
If you are keen on data integrity then don't touch any fs w/o data=ordered.
ext3 is still king wrt data=ordered, albeit slow.
Now XFS is fast, but doesn't support data=ordered. It seems that their
solution to the problem is to pass the burden onto hw by using barriers.
Maybe XFS can get away with this. Maybe.
Thanks!
--
Al
next prev parent reply other threads:[~2006-06-23 14:01 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 19:11 Large single raid and XFS or two small ones and EXT3? Chris Allen
2006-06-22 19:16 ` Gordon Henderson
2006-06-22 19:23 ` H. Peter Anvin
2006-06-22 19:58 ` Chris Allen
2006-06-22 20:00 ` Chris Allen
2006-06-23 8:59 ` PFC
2006-06-23 9:26 ` Francois Barre
2006-06-23 12:50 ` Chris Allen
2006-06-23 13:14 ` Gordon Henderson
2006-06-23 13:30 ` Francois Barre
2006-06-23 14:46 ` Martin Schröder
2006-06-23 14:59 ` Francois Barre
2006-06-23 15:13 ` Bill Davidsen
2006-06-23 15:34 ` Francois Barre
2006-06-23 19:49 ` Nix
2006-06-24 5:19 ` Neil Brown
2006-06-24 7:59 ` Adam Talbot
2006-06-24 9:34 ` David Greaves
2006-06-24 22:52 ` Adam Talbot
2006-06-25 13:06 ` Joshua Baker-LePain
2006-06-28 3:45 ` I need a PCI V2.1 4 port SATA card Guy
2006-06-28 4:29 ` Brad Campbell
2006-06-28 10:20 ` Justin Piszcz
2006-06-28 11:55 ` Christian Pernegger
2006-06-28 11:59 ` Gordon Henderson
2006-06-29 18:45 ` Bill Davidsen
2006-06-28 19:38 ` Justin Piszcz
2006-06-28 12:12 ` Petr Vyskocil
2006-06-25 14:51 ` Large single raid and XFS or two small ones and EXT3? Adam Talbot
2006-06-25 20:35 ` Chris Allen
2006-06-25 23:57 ` Bill Davidsen
2006-06-26 0:42 ` Adam Talbot
2006-06-26 14:03 ` Bill Davidsen
2006-06-24 12:40 ` Justin Piszcz
2006-06-26 0:06 ` Bill Davidsen
2006-06-26 8:06 ` Justin Piszcz
2006-06-23 15:17 ` Chris Allen
2006-06-23 14:01 ` Al Boldi [this message]
2006-06-23 16:06 ` Andreas Dilger
2006-06-23 16:41 ` Christian Pedaschus
2006-06-23 16:46 ` Christian Pedaschus
2006-06-23 19:53 ` Nix
2006-06-23 16:21 ` Russell Cattelan
2006-06-23 18:19 ` Tom Vier
2006-06-27 12:05 ` Large single raid... - XFS over NFS woes Dexter Filmore
2006-06-23 19:48 ` Large single raid and XFS or two small ones and EXT3? Nix
2006-06-25 19:13 ` David Rees
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=200606231701.44803.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).