Bug#583870: Acknowledgement (linux-image-2.6.26-2-686: inconsistencies in ext3 file systems)
On Mon, 31.05.2010 at 20:27:02 +0200, Toni Mueller <firstname.lastname@example.org> wrote:
> the problem only surfaced when the machine did not come up after an
> attempt to reboot (shutdown -r now).
> Trying to check the affected file system yields tons of these (almost
> 2000 lines):
> # 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.
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com