summaryrefslogtreecommitdiffstats
path: root/sparsify
diff options
context:
space:
mode:
authorRichard W.M. Jones <rjones@redhat.com>2012-08-18 22:27:17 +0100
committerRichard W.M. Jones <rjones@redhat.com>2012-08-19 15:35:14 +0100
commitcd1627e8041ffa06764ef82b984f4291660edcc9 (patch)
treefeec53743f66f951a1ccf28be46c543514e31c6a /sparsify
parentd67e6ea75dde6309ce4c6162a4a0429ab8d6709b (diff)
downloadlibguestfs-cd1627e8041ffa06764ef82b984f4291660edcc9.tar.gz
libguestfs-cd1627e8041ffa06764ef82b984f4291660edcc9.tar.xz
libguestfs-cd1627e8041ffa06764ef82b984f4291660edcc9.zip
FAQ: virt-sparsify and raw sparse output.
Diffstat (limited to 'sparsify')
-rw-r--r--sparsify/virt-sparsify.pod13
1 files changed, 13 insertions, 0 deletions
diff --git a/sparsify/virt-sparsify.pod b/sparsify/virt-sparsify.pod
index 14f7eecb..b716350b 100644
--- a/sparsify/virt-sparsify.pod
+++ b/sparsify/virt-sparsify.pod
@@ -25,6 +25,19 @@ Virt-sparsify can operate on any disk image, not just ones from
virtual machines. If a virtual machine has more than one attached
disk, you must sparsify each one separately.
+=head2 IMPORTANT NOTE ABOUT SPARSE OUTPUT IMAGES
+
+If the input is raw, then the default output is raw sparse. B<You
+must check the output size using a tool that understands sparseness>
+such as C<du -sh>. It can make a huge difference:
+
+ $ ls -lh test1.img
+ -rw-rw-r--. 1 rjones rjones 100M Aug 8 08:08 test1.img
+ $ du -sh test1.img
+ 3.6M test1.img
+
+(Compare the apparent size B<100M> vs the actual size B<3.6M>)
+
=head2 IMPORTANT LIMITATIONS
=over 4