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-next>] [day] [month] [year] [list]

Message-ID: <49EDF6E8.7070101@redhat.com>
Date:	Tue, 21 Apr 2009 11:40:08 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Thierry Vignaud <tvignaud@...driva.com>
CC:	Jeremy Sanders <jss@....cam.ac.uk>, linux-ext4@...r.kernel.org
Subject: Re: fsck.ext4: Group descriptors look bad... trying backup blocks...

Thierry Vignaud wrote:
> Eric Sandeen <sandeen@...hat.com> writes:
> 
>>>> 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.
>>> For the record, I reproduced this bug with 2.6.30-rc2-git6 on a new
>>> 1.5Tb disk. Formated as ext4, using relatime, copied 20Gb.
>>> On reboot, I got such errors.
>>> The hd was partitionned (all ext4) as:
>>> / (5Gb)  |  /usr (20Gb)  |  /pub (1.5Tb)
>>>
>>> The smaller system fses didn't saw those errors.
>> Can you provide a little more info on how you copied the 20Gb, and
>> exactly what the errors were?
> 
> I just copied some files from an USB hard disc with cp on the big
> partition (the one that showed the issues).
> For other system partitions (that showed _no_ problems) were filled with
> something like "rsync -rvltpx / /where/it/was/mounted"
> 
> Here's the fsck log:
> 
> 
>-----------------------------------------------------------------------

Wow, awful.

Could you send me dumpe2fs -h output of the large target device, as well
as an "e2image -r" image of the source filesystem?  That way I can
hopefully perfectly replicate your target filesystem as well as the data
you're using to populate it, try the cp myself, and see if I hit the
same thing.

e2image only sends metadata information, not data.  If you are concerned
about filenames, use -s to scramble them, though this *might* impact my
ability to reproduce it...

Thanks,
-Eric
--
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