Extracted image occupies more space than original
Posted: Mon Mar 13, 2017 11:45 pm
I created a backup from a Windows 10 volume, that was offline.
Then I restored the image to another, empty volume.
The restored Image on the second volume consumes about 3% more space than the original volume.
To double check, I created another backup of the extracted volume.
Comparing the file lists of both WIM Images showed that they are absolutely identical, as one would expect.
So where does the extra 3% space go?
Both volumes have the same cluster size (4K), so I can rule out that more slack space is wasted.
Could it be that Windows creates hard links upon Installation and that wimlib is unable to recreate these;
therefore making copies of the affected files?
Then I restored the image to another, empty volume.
The restored Image on the second volume consumes about 3% more space than the original volume.
To double check, I created another backup of the extracted volume.
Comparing the file lists of both WIM Images showed that they are absolutely identical, as one would expect.
So where does the extra 3% space go?
Both volumes have the same cluster size (4K), so I can rule out that more slack space is wasted.
Could it be that Windows creates hard links upon Installation and that wimlib is unable to recreate these;
therefore making copies of the affected files?