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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
