[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060717210710.GB6803@aitel.hist.no>
Date: Mon, 17 Jul 2006 23:07:11 +0200
From: Helge Hafting <helgehaf@...el.hist.no>
To: Christian Trefzer <ctrefzer@....de>
Cc: Xavier Roche <roche+kml2@...lead.com>, linux-kernel@...r.kernel.org
Subject: Re: reiserFS?
On Sun, Jul 16, 2006 at 06:28:31PM +0200, Christian Trefzer wrote:
> On Sun, Jul 16, 2006 at 06:16:31PM +0200, Xavier Roche wrote:
> > > It simply the best filesystem for many kinds of usage patterns.
> >
> > The most frightening too. Reiserfs might be suitable for very specific
> > appliactions, but to use it in production machine, you need to have
> > some guts.
> >
> > My last reiserfs partition was blown up two days ago, because of a bad
> > sector, plus a fatal oops, looping endlessly. This was the second
> > time, and the last one, as none of my ext3 filesystems *ever* had
> > similar problems, despite numerous other bad sector issues. Not
> > mentionning the funny "recovery" tool, which generally finishes to
> > trash your data.
>
> I don't quite understand. You are supposed to dd_rescue the whole block
> device to a working drive and use fsck on the copy. Whatever is lost in
> the process must of course be restored from a recent backup. But, as a
> friend of mine put it recently, people don't need backup, they only need
> restore ; )
>
Well, many a home user simply doesn't have a a spare block device of
the same size. The hassle of reinstalling instead of just waiting
out a fsck is something still.
The ext filesystems are nice in that they have spare superblocks,
if the main one dies from a bad sector, the spares still work
so you don't loose the entire fs to only a few damaged sectors.
> fsck on a faulty drive might cause even more damage - how do you know
> that other areas of the device are OK?
>
Somehow, that has saved my day quite a few times with ext2.
I only lost a few files, then went shopping for a new disk. :-)
Helge Hafting
-
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