[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060806225912.GC4205@ucw.cz>
Date: Sun, 6 Aug 2006 22:59:12 +0000
From: Pavel Machek <pavel@....cz>
To: David Masover <ninja@...phack.com>
Cc: "Horst H. von Brand" <vonbrand@....utfsm.cl>,
Bernd Schubert <bernd-schubert@....de>,
reiserfs-list@...esys.com, Jan-Benedict Glaw <jbglaw@...-owl.de>,
Clay Barnes <clay.barnes@...il.com>,
Rudy Zijlstra <rudy@...ons.demon.nl>,
Adrian Ulrich <reiser4@...nkenlights.ch>, ipso@...ppymail.ca,
reiser@...esys.com, lkml@...productions.com, jeff@...zik.org,
tytso@....edu, linux-kernel@...r.kernel.org
Subject: Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion
On Tue 01-08-06 11:57:10, David Masover wrote:
> Horst H. von Brand wrote:
> >Bernd Schubert <bernd-schubert@....de> wrote:
>
> >>While filesystem speed is nice, it also would be great
> >>if reiser4.x would be very robust against any kind of
> >>hardware failures.
> >
> >Can't have both.
>
> Why not? I mean, other than TANSTAAFL, is there a
> technical reason for them being mutually exclusive? I
> suspect it's more "we haven't found a way yet..."
What does the acronym mean?
Yes, I'm afraid redundancy/checksums kill write speed, and you need
that for robustness...
You could have filesystem that can be tuned for reliability and tuned
for speed... but you can't have both in one filesystem instance.
--
Thanks for all the (sleeping) penguins.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists