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

[Mads Kiilerich]

Alexander Todorov wrote, On 08/15/2009 10:39 PM:
> 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 ?
>    

Perhaps it is because unused space might contain old data which probably 
compresses badly. By doing it this way the extended space will be 
initialized with zeroes which can be compressed to (almost) nothing, and 
the compressed image of the specified size thus doesn't take up more 
space than if it had the minimal size.

Why is that a problem?

/Mads