* Josh Coates [Sat, 8 Jan 2005 at 22:16 -0700] > > stuporglue: > >The purpose though was to zero out sections of the disk before compressing > (not just for dd-ing). > > ah - i see. when andrew posted his three suggestions, they appeared to be > independent of each other. > > so, the rationale behind this is to effectively "remove" old, unused blocks > by forcing the file system to re-allocate them for your big "zero" file that > you create. then, (whether you actually delete them or not) if you compress > all the blocks on the device, the zero blocks will of course compress > better. > > this now makes sense. of course, compressing a disk-to-disk copy using dd > is silly anyway, so this moot. ;-)
Compressing would be useful in some cases, but not all. It would indeed be pointless for a direct disk-to-disk replication. But if instead of writing the to the target disk you were saving the image within a filesystem (disk.img) then those empty spaces (and there are usually a lot, filesystems aren't generally full) would compress quite nicely, and that also leaves a lot less write time on the target disk. This would have a huge effect if both disks were on the same channel, or same disk on different partitions. The same benefit would hold in the reverse as well. Von Fugal
signature.asc
Description: Digital signature
-------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
