linux-ext4 - e2fsck dies with error "this should never happen!!!"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 22 Feb 2008 13:07:13 +0100
From:	Bas van Schaik <bas@...es.nl>
To:	linux-ext4@...r.kernel.org
Subject: e2fsck dies with error "this should never happen!!!"

Hi all,

Currently, I have a big problem: e2fsck refuses to fix my currupted
filesystem...

The filesystem (about 3TB) is created on an LVM LV, which spans a number
of RAID5 arrays, for which the underlying devices are imported using ATA
over Ethernet. Because of some strange network failure, the filesystem
got corrupted and was remounted read-only.

e2fsck presented me really _a lot_ of errors, especially much duplicated
blocks. After fixing them all, e2fsck restarts the check and after a
while dies with "XXX should never happen!!!". The complete output:

> e2fsck 1.40-WIP (14-Nov-2006)
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Directory inode 268451937 has an unallocated block #1.  Allocate? yes
>
> Directory inode 268451941 has an unallocated block #1.  Allocate? yes
>
> Directory inode 268451945 has an unallocated block #1.  Allocate? yes
>
> Directory inode 268451949 has an unallocated block #1.  Allocate? yes
>
> Directory inode 268451953 has an unallocated block #1.  Allocate? yes
>
> Directory inode 268451957 has an unallocated block #1.  Allocate? yes
>
> Directory inode 268451961 has an unallocated block #1.  Allocate? yes
>
> Directory inode 268451965 has an unallocated block #1.  Allocate? yes
>
> Directory inode 268451969 has an unallocated block #1.  Allocate? yes
>
> Directory inode 268451973 has an unallocated block #1.  Allocate? yes
>
> Directory inode 268451977 has an unallocated block #1.  Allocate? yes
>
> Directory inode 268451981 has an unallocated block #4.  Allocate? yes
>
> XXX should never happen!!!
> Aborted
>   

Furthermore I'm running the default Debian stable kernel 2.6.18.

When trying to mount the damaged filesystem and removing the directories
which were supposed to have problems (I saw some output about those
directories in earlier e2fsck runs), the filesystem of course reports
problems:

> # dmesg | tail
> kjournald starting.  Commit interval 10 seconds
> EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
> EXT3 FS on loop0, internal journal
> EXT3-fs: mounted filesystem with writeback data mode.
> EXT3-fs error (device loop0): ext3_free_inode: bit already cleared for
> inode 275087393
> Remounting filesystem read-only
>   

Can anyone please help me fix this filesystem? I will be on vacation
next week, so my reply might be a little bit late... Thanks!

Regards,

  -- Bas



-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html