From: Carlos Maiolino <cmaiolino@redhat.com>
To: linux-ext4@vger.kernel.org
Cc: Carlos Maiolino <cmaiolino@redhat.com>
Subject: [PATCH] Add better example about how to compress e2image raw image
Date: Fri, 23 Sep 2011 15:47:52 -0300 [thread overview]
Message-ID: <1316803672-25550-1-git-send-email-cmaiolino@redhat.com> (raw)
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@redhat.com>
---
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
next reply other threads:[~2011-09-23 18:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 18:47 Carlos Maiolino [this message]
2011-09-23 20:24 ` [PATCH] Add better example about how to compress e2image raw image Andreas Dilger
2011-09-23 20:51 ` Carlos Maiolino
2011-09-24 16:31 ` Ted Ts'o
2011-09-26 12:13 ` Carlos Maiolino
2011-09-26 12:22 ` Bernd Schubert
2011-09-26 16:25 ` Eric Sandeen
2011-09-26 16:24 ` Eric Sandeen
2011-09-26 19:23 ` Ted Ts'o
2011-09-26 19:36 ` Carlos Maiolino
2011-09-26 20:01 ` Amir Goldstein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1316803672-25550-1-git-send-email-cmaiolino@redhat.com \
--to=cmaiolino@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).