Re: corrupted ext4 1000gb filesystem (2.6.32, debian stable)

[Luke Kenneth Casson Leighton]

On Tue, Aug 2, 2011 at 1:15 AM, Luke Kenneth Casson Leighton
<luke.leighton@xxxxxxxxx> wrote:

> ok, um... i have a bit more information about this situation, to
> report. Âtwo consecutive runs of fsck.ext4, and the filesystem still
> reports errors after the first run "corrected" all errors. i'd say
> that was a bit serious.

 rright - apologies but i've located the likely source of the problem
- e2fsck.  the issue is that the bitmaps for the 3-way RAID1 mirror
were corrupted.  thus, the filesystem would be fixed by e2fsck, only
to be completely buggered up by picking wildly inappropriate sections
of the drive... that presumably by either bad luck or by a powercut
and writes occurring at the time happened to be on inode blocks.

 whilst it is not entirely possible, due to this being a complex
interdependent set of empirical observations, to rule out ext4, i
believe it's safe to say that ext4 is not a high candidate, and i
apologise for taking up peoples' time.  now all i can hope for is that
the data isn't completely buggered.. :)

l.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/