I've seen the same issue. At home I made some disk images for qemu. $ dd if=/dev/zero of=drivec.img count=0 seek=4096 bs=1M 0+0 records in 0+0 records out 0 bytes transferred in 0.000228 seconds (0 bytes/sec) $ ls -la total 8 drwxr-xr-x 2 supaplex supaplex 4096 2006-02-08 16:53 . drwx------ 62 supaplex supaplex 4096 2006-02-08 16:53 .. -rw-r--r-- 1 supaplex supaplex 4294967296 2006-02-08 16:53 drivec.img
This shows it is using 8kb on disk (real), and is 4G (virtual;sparse) $dd if=/dev/urandom of=drivec.img conv=notrunc bs=1M count=100 $ ls -lA total 102504 -rw-r--r-- 1 supaplex supaplex 4294967296 2006-02-08 17:16 drivec.img $ cd .. $ tar -Szcvf qemu-win98.tar.gz win98/ win98/ win98/drivec.img $ ls -l qemu-win98.tar.gz -rw------- 1 supaplex supaplex 104874582 2006-02-08 17:19 qemu-win98.tar.gz $ tar -Szxvf qemu-win98.tar.gz win98/ win98/drivec.img $ ls -l win98 total 0 -rw-r--r-- 1 supaplex supaplex 0 2006-02-08 17:16 drivec.img I think the issue resides between the extracted stream and the extraction (tar). $ gunzip qemu-win98.tar.gz $ ls -l qemu-win98.tar -rw------- 1 supaplex supaplex 104867840 2006-02-08 17:19 qemu-win98.tar $ tar Sxvf qemu-win98.tar win98/ win98/drivec.img $ ls -l win98/ total 0 -rw-r--r-- 1 supaplex supaplex 0 2006-02-08 17:16 drivec.img It's sparse alright. A little *too* sparse. hehe :) Thanks, -- Scott Edwards Systems Administrator ArosNet Internet Services - http://www.aros.net 28 South 400 East; Salt Lake City, UT 84111-1804; 801.532.AROS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
