Hi Theodore, Thanks for your reply.
Right, we were using "resize2fs -M" to shrink our images(so it's nearly full), then grow it at first boot after flashed to the embedded device. And the online resize works perfectly, i'll use that :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1796788 Title: resize2fs: Illegal indirect block found while trying to resize Status in e2fsprogs package in Ubuntu: Confirmed Bug description: The new resize2fs(1.43+) failed to resize attached image file, and e2fsck didn't report any error before the resizing. Test steps: 1/ e2fsck -fy userdata.img 2/ resize2fs userdata.img 220M Result: When using resize2fs from e2fsprogs 1.43+(tested 1.43.4/1.43.5/1.44.4), it would abort with: Resizing the filesystem on userdata.img to 225280 (1k) blocks. resize2fs: Illegal indirect block found while trying to resize userdata.img Please run 'e2fsck -fy userdata.img' to fix the filesystem after the aborted resize operation. More information: 1/ The image is generated on xenial with genext2fs 2/ It works well on xenial with e2fsprogs 1.42.13-1ubuntu1 3/ It works well when resizing with a size less than 220M, for example "resize2fs userdata.img 219M" 4/ online resize works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1796788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
