The current example in the man page uses bzip2 to compress the raw image file created by the e2image, but, bzip2 does not honors sparse files, which causes the image to have the same size of the filesystem. Using tar together with bzip2 will make the compressed file to honor the sparsed file, which makes it more transportable than the current one if the filesystem is large. Signed-off-by: Carlos Maiolino <cmaiolino@xxxxxxxxxx> --- misc/e2image.8.in | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/misc/e2image.8.in b/misc/e2image.8.in index 74d2a0b..fcf3d20 100644 --- a/misc/e2image.8.in +++ b/misc/e2image.8.in @@ -115,7 +115,7 @@ as part of bug reports to e2fsprogs. When used in this capacity, the recommended command is as follows (replace hda1 with the appropriate device): .PP .br -\ \fBe2image \-r /dev/hda1 \- | bzip2 > hda1.e2i.bz2\fR +\ \fBe2image \-r /dev/hda1 hda1.e2i && tar Sjcvf e2i.tar.bz2 hda1.e2i\fR .PP This will only send the metadata information, without any data blocks. However, the filenames in the directory blocks can still reveal -- 1.7.5.2 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
