Hi, When I tried to resize a loop ext4 image to minimum, I couldn't get correct result. Please see below test and results: 1. e2fsprogs 1.43-WIP version: mke2fs -F -t ext4 foo.img 512M mount foo.img mnt1 dd if=/dev/zero of=mnt1/test bs=1M count=350 df | grep mnt1 /dev/loop0 499656 358796 104164 78% /mnt1 umount mnt1 e2fsck -f foo.img resize2fs -M foo.img resize2fs 1.43-WIP (29-Mar-2015) Resizing the filesystem on foo.img to 129175 (4k) blocks. The filesystem on foo.img is now 129175 (4k) blocks long. ls -al foo.img -rw-r--r-- 1 root root 529100800 Apr 29 08:00 foo.img 2. e2fsprogs 1.42.9 version: mke2fs -F -t ext4 bar.img 512M mount bar.img mnt2 dd if=/dev/zero of=mnt2/test bs=1M count=350 umount mnt2 e2fsck -f bar.img resize2fs -M bar.img resize2fs 1.42.9 (28-Dec-2013) Resizing the filesystem on bar.img to 103592 (4k) blocks. The filesystem on bar.img is now 103592 blocks long. ls -al bar.img -rw-r--r-- 1 root root 424312832 Apr 29 08:04 bar.img 1.43-WIP version: 529100800 -> 529100800 1.42.9 version: 529100800 -> 424312832 Furthermore, the resizing to minimum was failed if the loop image was filled over 84%. I found it was changed since (45a78b8 resize2fs: refine minimum required blocks for flex_bg file systems) Is it correct or something's wrong? Best Regards, Chanho Park -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
