From: Ted Ts'o <tytso@mit.edu>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org, sandeen@redhat.com, adilger@dilger.ca
Subject: Re: [PATCH 2/4 v3] e2image: Add support for qcow2 format
Date: Wed, 18 May 2011 12:17:51 -0400 [thread overview]
Message-ID: <20110518161751.GC29368@thunk.org> (raw)
In-Reply-To: <1305718615-5991-2-git-send-email-lczerner@redhat.com>
On Wed, May 18, 2011 at 01:36:53PM +0200, Lukas Czerner wrote:
> This commit adds support for exporting filesystem into QCOW2 image
> format. Like sparse format this saves space, by writing only necessary
> (metadata blocks) into image. Unlike sparse image, QCOW2 image is NOT
> sparse, hence does not change its size by copying with not-sparse-aware
> tools.
>
> New options '-Q' has been added to tell the e2image to use QCOW2 as an
> output image format. QCOW2 supports encryption and compression, however
> e2image so far does no support such features, however you can still
> scramble filenames with '-s' option.
>
> Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Applied to the e2fsprogs branch, with a lot of whitespace fixes.
- Ted
next prev parent reply other threads:[~2011-05-18 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 11:36 [PATCH 1/4] e2fsprogs: Add memory allocation and zero-out helpers Lukas Czerner
2011-05-18 11:36 ` [PATCH 2/4 v3] e2image: Add support for qcow2 format Lukas Czerner
2011-05-18 16:17 ` Ted Ts'o [this message]
2011-05-18 16:20 ` Lukas Czerner
2011-05-18 20:59 ` Andreas Dilger
2011-05-18 11:36 ` [PATCH 3/4 v3] e2image: Support for conversion QCOW2 image into raw Lukas Czerner
2011-05-18 12:20 ` [PATCH 3/4 v4] " Lukas Czerner
2011-05-18 16:18 ` Ted Ts'o
2011-05-18 12:23 ` [PATCH 3/4 v3] " Lukas Czerner
2011-05-18 12:22 ` [PATCH 1/4] e2fsprogs: Add memory allocation and zero-out helpers Lukas Czerner
[not found] ` <1305718615-5991-4-git-send-email-lczerner@redhat.com>
2011-05-18 16:19 ` [PATCH 4/4 v3] tests: New i_e2image test to validate image creation/conversion Ted Ts'o
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=20110518161751.GC29368@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.