On Fri, Jul 08, 2016 at 07:39:35AM +0200, Ulrich Möhrke wrote:
> Hello Ted and others,
>
> many thanks for the answer and sorry that I did not answer before. I
> have not been at home for a week and I had to understand the work with
> sparse files before answering.
>
> I will send the requested info and the file system dump.
>
> Output of fsck:
> fsck from util-linux 2.28
> e2fsck 1.43.1 (08-Jun-2016)
> linuxroot: clean, 491253/10412032 files, 13204522/41632768 blocks
>
> Output of dumpe2fs is attached as file dumpe2fs.out.
>
> I created an image sda6.img with e2image. The error happened at this
> file too ("resize2fs -p sda6.img 162336768K" dumps).
> I also created an image with e2image -rs (sda6_rs.img). This has been
> corrupted. After running fsck twice (ones with option -p, once without)
> it shows the same error with resize2fs as the original file system
> (sda6_rs_fsck.img).
> I uploaded compressed versions of the files to
> https://drive.google.com/folderview?id=0B5YpWNZ90f2EWEZvU1A3OU1zQU0&usp=sharing
Thanks for uploading the files and my apologies for my not getting
back to you earlier. I've confirmed that this bug is the same as one
which was fixed a few weeks ago:
commit 3d6fc974831a360aee460e54c442538445f3017c
Author: Theodore Ts'o <ty...@mit.edu>
Date: Wed Aug 10 15:49:35 2016 -0400
resize2fs: fix crash when there is an ea block and no blocks to migrate
This fixes a bug introduced in 1.43 by commit fb47b94fffc: "resize2fs:
rewrite extent/dir/ea block checksums when migrating". If there is an
extended attribute block and there are no blocks that need to migrate,
we will crash.
The bug was caused by a botched De Morgan's transformation.
Signed-off-by: Theodore Ts'o <ty...@mit.edu>
This commit is in e2fsprogs 1.42.2.
- Ted
