[Fedora-livecd-list] Why resize back ext3fs.img to bigger size.

[Alexander Todorov]

Hi,
in fs.py in ExtDiskMount.resparse() function we resize and truncate the image to
minimum possible size (i.e. ext3 becomes 100% full) and then resize it back to
the size specified in kickstart. In most cases this results in ext3fs.img which
when mounted has lots of free space on it.


Why is that ? It can be avoided by this simple patch:

---------------------------------
 imgcreate/fs.py |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/imgcreate/fs.py b/imgcreate/fs.py
index 563b7a9..50ec5e7 100644
--- a/imgcreate/fs.py
+++ b/imgcreate/fs.py
@@ -470,7 +470,6 @@ class ExtDiskMount(DiskMount):
         self.cleanup()
         minsize = self.__resize_to_minimal()
         self.disk.truncate(minsize)
-        self.__resize_filesystem(size)
         return minsize

 class DeviceMapperSnapshot(object):