The ext2resize utility apparently doesn't handle ext3 filesystems correctly and damages them. Reproducible: Always Steps to Reproduce: # create 200MB ext3 filesystem dd if=/dev/zero of=test.img bs=1M count=200 losetup /dev/loop0 test.img mke2fs -j /dev/loop0 # everything is OK fsck.ext3 -f /dev/loop0 # enlarge filesystem by 50MB losetup -d /dev/loop0 dd if=/dev/zero of=test.img bs=1M count=50 seek=200 losetup /dev/loop0 test.img ext2resize /dev/loop0 # this works: resize2fs /dev/loop0 # fsck reports filesystem errors fsck.ext3 -f /dev/loop0 # clean up losetup -d /dev/loop0 rm test.img Actual Results: The second fsck.ext3 reports filesystem errors: - Resize inode not valid - Block bitmap differences - Free blocks count wrong for group #0 and so forth. Expected Results: The second fsck.ext3 reports no filesystem errors. If the filesystem is resized using 'resize2fs' from sys-fs/e2fsprogs everything works as expected. As the packages seems unmaintained (the latest release is from September 30, 2004) and ext2resize can be replaced by resize2fs please mask this package to avoid possible data loss caused by this tool.
done
