© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I just verified that resizing an image now also increases number of inodes.
$ truncate my.img --size 1M
$ mke2fs -F my.img >/dev/null
mke2fs 1.41.9 (22-Aug-2009)
$ dumpe2fs my.img | grep 'Inode count'
dumpe2fs 1.41.9 (22-Aug-2009)
Inode count: 128
$ truncate my.img --size 100M
$ resize2fs my.img 100M
resize2fs 1.41.9 (22-Aug-2009)
Resizing the filesystem on my.img to 102400 (1k) blocks.
The filesystem on my.img is now 102400 blocks long.
$ dumpe2fs my.img | grep 'Inode count'
dumpe2fs 1.41.9 (22-Aug-2009)
Inode count: 1664
So, my proposed script has little to no value. The benefit to it now is that it works on shrink or grow. We'll need to change Matt's script to determine if input size is < or > than current size, and perform the truncate after or before the resize. Then, I think its done.