1. Although 2.5/20 is currently in use it could be that much of the rest of the 20GB was once written to and now does not contain strictly 0000000's. In this case the compression will not be as great as it could be. You may want to use the suggested procedure for Zero-izing your disk before turning it into a compressed image. This will have to be done for each partition on the disk.
----------------------------------------------- On the live system, just create a huge file:
dd if=/dev/zero of=filler-file
After a while, the dd will error out with a "disk full" error.
Then, do a couple of syncs, and remove the file.
sync sync rm filler-file -----------------------------------------------
2. lzop is designed for speed and not compression. Try setting the compression level to -7, -8, or -9 for better compression.
Lee
-----Original Message----- From: udpcast-bounces@udpcast.linux.lu [mailto:udpcast-bounces@udpcast.linux.lu] On Behalf Of cmonster@icehouse.net Sent: Tuesday, July 27, 2004 4:36 PM To: udpcast@udpcast.linux.lu Subject: [Udpcast] Image size bigger that actual space used
I have been trying to send an image to my server. The hard drive on the computer that I am sending from is 20 gig with 2.5 used. I turn on lzop compession and send the image to the server. But the image file endes up being 8.2 gigs. Any idea why it would be that big?
Thanks again for your help Kevin _______________________________________________ Udpcast mailing list Udpcast@udpcast.linux.lu http://udpcast.linux.lu/mailman/listinfo/udpcast