[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200607312314.37863.bernd-schubert@gmx.de>
Date: Mon, 31 Jul 2006 23:14:37 +0200
From: Bernd Schubert <bernd-schubert@....de>
To: reiserfs-list@...esys.com
Cc: Jan-Benedict Glaw <jbglaw@...-owl.de>,
Clay Barnes <clay.barnes@...il.com>,
Rudy Zijlstra <rudy@...ons.demon.nl>,
Adrian Ulrich <reiser4@...nkenlights.ch>,
vonbrand@....utfsm.cl, 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 Monday 31 July 2006 21:29, Jan-Benedict Glaw wrote:
>
> The point is that it's quite hard to really fuck up ext{2,3} with only
> some KB being written while it seems (due to the
> fragile^Wsophisticated on-disk data structures) that it's just easy to
> kill a reiser3 filesystem.
>
Well, I was once very 'luckily' and after a system crash (*) e2fsck put all
files into lost+found. Sure, I never experienced this again, but I also never
experienced something like this with reiserfs. So please, stop this kind of
FUD against reiser3.6.
While filesystem speed is nice, it also would be great if reiser4.x would be
very robust against any kind of hardware failures.
(*) The problem was a specific mainboard + video-card + driver combination. As
soon as X started up, the system entirely crashed. I don't believe many bytes
were written, but I also can't prove it.
--
Bernd Schubert
PCI / Theoretische Chemie
Universität Heidelberg
INF 229
69120 Heidelberg
-
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