Note a file system which is significantly shrunk --- which tends to be
the case with resize2fs -M --- is going to have files fragmented which
will have performance implications. It's not clear to me what you are
trying to optimize for --- I assume you're just wanting to save on
download
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
Yep, I can reproduce the problem. It bisected to:
commit 538ef363261b4f851ca69f342336aa896e24eb27 (refs/bisect/bad)
Author: Darrick J. Wong
Date: Sun Dec 14 22:13:09 2014 -0500
resize2fs: don't play stupid games with the block count
While it may be true that playing games with
** Description changed:
-
- The new resize2fs(1.43+) failed to resize attached image file, and e2fsck
didn't report any error before the resizing.
+ The new resize2fs(1.43+) failed to resize attached image file, and
+ e2fsck didn't report any error before the resizing.
Test steps:
- 1/
** Description changed:
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 -M 220M
+ 2/ resize2fs userdata.img 220M
Result:
When using resize2fs
5 matches
Mail list logo