From: Francois Barre <francois.barre@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Fwd: Linux MD raid5 and reiser4... Any experience ?
Date: Thu, 5 Jan 2006 12:21:56 +0100 [thread overview]
Message-ID: <fd8d0180601050321k19f12f53r@mail.gmail.com> (raw)
In-Reply-To: <87oe2r2d93.fsf@rimspace.net>
2006/1/5, Daniel Pittman <daniel@rimspace.net>:
> Francois Barre <francois.barre@gmail.com> writes:
>
> G'day Francois.
>
> > Well, I think everything is in the subject... I am looking at this
> > solution for a 6*250GB raid5 data server, evolving in a 12*250 rai5 in
> > the months to come... Performance is absolutely not a big issue for
> > me, but I would not appreciate any data loss.
>
> If your key interest is data integrity, and you don't care a fig about
> performance, you would be much better off using ext3 on that filesystem.
>
> Depending on the test, ext3 may not do better than other filesystems,
> but it is really quite hard to go past the long history of reliability
> and stability that it has.
>
[...]
Well, as far as I understood it (that is, not so far :-p), reiser4
seemed to have a stronger and more efficient journal than ext3. That
is not what everyone believes, but reiser4 was to be designed that way
more or less... But I guess that ext3 and its very-heavily-tested
journal can still be more trusted than any newcomer.
Truth is, I would have been glad to play with reiser4 on a large
amount of data, just because I was interrested on the theories behind
it (including the database-filesystem strange wedding Hans tried to
organize). Maybe it's too great a risk for a production system.
Well, anyway, thanks for the advice. Guess I'll have to stay on ext3
if I don't want to have nightmares...
Best regards,
F.-E.B.
next prev parent reply other threads:[~2006-01-05 11:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fd8d0180601050104x15079396h@mail.gmail.com>
2006-01-05 9:06 ` Fwd: Linux MD raid5 and reiser4... Any experience ? Francois Barre
2006-01-05 10:14 ` Daniel Pittman
2006-01-05 11:21 ` Francois Barre [this message]
2006-01-05 11:31 ` Gordon Henderson
2006-01-06 6:33 ` Daniel Pittman
2006-01-06 9:47 ` Simon Valiquette
2006-01-06 10:50 ` Francois Barre
2006-01-06 19:28 ` Forrest Taylor
2006-01-06 11:03 ` Kanotix crashed my raid PFC
2006-01-06 12:02 ` PFC
2006-01-06 12:08 ` PFC
2006-01-06 22:01 ` PFC
[not found] ` <200601090803.03588.mlaks@verizon.net>
2006-01-09 18:30 ` PFC
2006-01-06 19:05 ` Fwd: Linux MD raid5 and reiser4... Any experience ? Mike Hardy
2006-01-08 2:53 ` Daniel Pittman
2006-01-05 11:26 ` berk walker
2006-01-05 11:35 ` Francois Barre
2006-01-05 11:43 ` Gordon Henderson
2006-01-05 11:59 ` berk walker
2006-01-05 13:13 ` Bill Rugolsky Jr.
2006-01-05 13:38 ` John Stoffel
2006-01-05 14:03 ` Francois Barre
2006-01-05 18:55 ` John Stoffel
2006-01-06 9:08 ` Francois Barre
2006-01-06 10:49 ` Andre Majorel
2006-01-09 8:00 ` Molle Bestefich
2006-01-09 8:16 ` Gordon Henderson
2006-01-09 9:00 ` Francois Barre
2006-01-09 9:24 ` Molle Bestefich
2006-01-05 17:32 Andrew Burgess
2006-01-05 17:50 ` Francois Barre
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=fd8d0180601050321k19f12f53r@mail.gmail.com \
--to=francois.barre@gmail.com \
--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 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.