Bug#583870: inconsistencies in ext3 file systems

[Jonathan Nieder <jrnieder@gmail.com>]

Hi Toni,

Toni Mueller wrote:
> On Mon, 31.05.2010 at 20:27:02 +0200, Toni Mueller <support@oeko.net> wrote:

>> # fsck -p /dev/mapper/uv0-srv
>> fsck 1.41.3 (12-Oct-2008)
>> /dev/mapper/uv0-srv contains a file system with errors, check forced.
>> /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (5) has invalid depth (2)
>> /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (5) has bad max hash
>> /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (5) not referenced
>
> it turns out that only one directory was affected. This directory
> contains 488984 files. I don't think that having many files in a
> directory should be an error, only (possibly) a performance problem.
> But in no case should the file system become corrupted, imho.

Well, yes, that's clearly true. :)

Do you still have the corrupted filesystem available?  It might be
interesting to try to do a post-mortem analysis on it --- please see
the RAW IMAGE FILES section of e2image(8) and let us know if that
will be possible.

Sorry for the long silence.

Thanks and hope that that helps,
Jonathan