linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Robin Dong <hao.bigrat@gmail.com>
Cc: linux-ext4@vger.kernel.org, Robin Dong <sanbai@taobao.com>
Subject: Re: [PATCH 1/2] mksparse: build sparse file from compressed e2image file.
Date: Mon, 28 Feb 2011 13:26:04 -0500	[thread overview]
Message-ID: <20110228182604.GC28617@thunk.org> (raw)
In-Reply-To: <1298860514-615-1-git-send-email-hao.bigrat@gmail.com>

On Mon, Feb 28, 2011 at 10:35:13AM +0800, Robin Dong wrote:
> From: Robin Dong <sanbai@taobao.com>
> 
> [Purpose]
> After we make a image-file by e2image like:
> #e2image -r /dev/hda1 - | bzip2 > hda1.bz2
> we copy the bz2 file to remote host and extract it:
> #bunzip2 hda1.bz2 
> the unzipped hda1 file will not be a sparse file and the space occupied
> by it is as large as the real /dev/hda1 filesystem.
> 
> Therefore a tool to transform a raw-file to a sparse-file is necessary.
> This Patch is a first attempt to provide such a tool which is called
> 'mksparse' so far.

I guess you didn't find /usr/src/e2fsprogs/contrib/make-sparse.c file
that I had written a while back.  I never did write a man page or
usage manual, or the rest of the niceties that go into a supported
program, but it's there.  :-)

I've never been completely convinced this was functionality was one
that should be included in the e2fsprogs as a supported program and
shipped with distributions.  It is useful, though, and I've certainly
used make-sparse.c many times in the past, so I'm willing to be
convinced otherwise.

						- Ted

      parent reply	other threads:[~2011-02-28 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28  2:35 [PATCH 1/2] mksparse: build sparse file from compressed e2image file Robin Dong
2011-02-28  2:35 ` [PATCH 2/2] add manual for tool 'mksparse' Robin Dong
2011-02-28  3:09 ` [PATCH 1/2] mksparse: build sparse file from compressed e2image file Yongqiang Yang
2011-02-28 13:24 ` Lukas Czerner
2011-02-28 18:26 ` Ted Ts'o [this message]

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=20110228182604.GC28617@thunk.org \
    --to=tytso@mit.edu \
    --cc=hao.bigrat@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sanbai@taobao.com \
    /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).