Timeline for reasons for a dd image of an almost-empty drive not be small after gzip
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 27, 2013 at 2:04 | vote | accept | gcb | ||
| Feb 27, 2013 at 2:01 | answer | added | Grizly | timeline score: 3 | |
| Feb 25, 2013 at 21:49 | review | Close votes | |||
| Feb 26, 2013 at 0:27 | |||||
| Feb 25, 2013 at 21:28 | comment | added | gcb | turned out that the install, for some reason, scattered data all over the disk. I redid the cat /dev/zero > /mounted_drive/zero after the install and then removed the file and redid the dd, turned out to be a 1.3Gb file after gzip. | |
| Feb 25, 2013 at 16:52 | comment | added | derobert | I guess if you enabled full-disk encryption, that'd explain it. Or maybe if you ran badblocks (in write-destructive mode) as part of making the filesystems. | |
| Feb 25, 2013 at 9:42 | history | asked | gcb | CC BY-SA 3.0 |