On Sun, 6 Aug 2006, Matthias Andree wrote:
> (changing subject to catch Ted's attention)
> Bodo Eggert schrieb am 2006-08-05:
> > - I have an ext3 that can't be fixed by e2fsck (see below). fsck will fix
> > some errors, trash some files and leave a fs waiting to throw the same
> > error again. I'm fixing it using mkreiserfs now.
>
> If such a bug persists with the latest released e2fsck version - you're
> not showing e2fsck logs - I'm rather sure Ted Ts'o would like to have a
> look at your file system meta data in order to teach e2fsck how to fix
> this.
Unfortunately I had no time to generate a fsck log before doing mkfs, nor
did I catch the fsck log before. The best thing I could do at that moment
was appending an except from thr log hoping it can be usefull.
My main intention was posting a differently biased view on fs robustness.
> I've seen sufficient releases of reiserfsck that couldn't fix certain
> bugs, too, so trying with the latest version of the respective tools is
> a must.
It was the latest version I found.
--
A. Top posters
Q. What's the most annoying thing on Usenet?
