linux-ext4 - Re: fsck.ext4: Group descriptors look bad... trying backup blocks...

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <gshfgl$o6m$1@ger.gmane.org>
Date:	Mon, 20 Apr 2009 10:33:09 +0100
From:	Jeremy Sanders <jss@....cam.ac.uk>
To:	linux-ext4@...r.kernel.org
Subject:  Re: fsck.ext4: Group descriptors look bad... trying backup blocks...

Eric Sandeen wrote:

> Jeremy, if you're willing, could you upgrade to the 2.6.29 kernel that's
> in F10 updates-testing?  That way the ext4 code is a bit more of a
> recent, common codebase.  Also, if this is a test fs, re-mkfs'ing from
> scratch might not be a bad way to go.
> 
> Depending on how hard it is to reproduce, it may also be interesting to
> try a filesystem just shy of 8TB (2^31) blocks in case there is some
> 32-bit wrap-around there, since you're at 8.2T....

I wasn't able to trivially reproduce the problem with the old kernel, but I 
updated to 2.6.29.1-30.fc10.x86_64 in updates testing. This introduced some 
further problems with a USB issue and some sort of stack dump probably 
associated with the r8169 driver (see bugzilla).

However, the system seems to mostly work, so I recreated the ext4 device, 
I've just run my backup script again and fsck'd the device. It seems the 
problem is reproducible with the new kernel:

[root@...ck2 ~]# fsck /dev/md0
fsck 1.41.4 (27-Jan-2009)
e2fsck 1.41.4 (27-Jan-2009)
fsck.ext4: Group descriptors look bad... trying backup blocks...
Group descriptor 0 checksum is invalid.  Fix<y>?

Looks like there's a real problem in ext4 causing this under certain 
circumstances (unless an obscure hardware error is somehow giving the same 
problem).

To cause this, all I did was rsync a set of directories to the disk. No hard 
link trees were created.

Jeremy

-- 
Jeremy Sanders <jss@....cam.ac.uk>   http://www-xray.ast.cam.ac.uk/~jss/
X-Ray Group, Institute of Astronomy, University of Cambridge, UK.
Public Key Server PGP Key ID: E1AAE053

--
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