linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Czerner <lczerner@redhat.com>
To: tytso@mit.edu
Cc: adilger@dilger.ca, sandeen@redhat.com, lczerner@redhat.com,
	linux-ext4@vger.kernel.org
Subject: [PARCH 0/1 RFC] e2image: Add support for QCOW2 image format
Date: Wed,  1 Dec 2010 18:41:48 +0100	[thread overview]
Message-ID: <1291225309-10750-1-git-send-email-lczerner@redhat.com> (raw)

Hi, all

As Ted suggested on LPC I started to play with e2image to add support for
exporting images in QCOW2 format (http://en.wikipedia.org/wiki/Qcow2). The
advantage of this format is mainly that the resulting image is quite small
(because we write only the metadata blocks) and it is not sparse unlike
"sparse" image format.

I am presenting you an initial parch, which works for me quite nicely, however
so far it did received just limited testing. Nevertheless you can try it simply
by invoking e2image with '-q' parameter like this:

	e2image -q /dev/sda1 myimage

or you can add '-s' option so the file names are scrambled. To mount that qcow2
image I usually use 'qemu-nbd':

	modprobe nbd max_part=8
	qemu-nbd --connect=/dev/nbd0 myimage
	mount -o ro /dev/nbd0 /mnt/test/

However I have experienced some problems with qemu-nbd from time to time. Also
for some reason, when you mount the image read-write, you'll destroy it. So far
I was not able to figure out why (I did not tried at all to be honest), it may
be problem in my image format or even in qemu itself, so if you have any idea,
please let me know.

QCOW2 format supports other neat features like compression, encryption and
snapshots. None of those feature are supported in this patch and the question
is, do we need it ? I can imagine for example snapshots to be useful for
roll-back changes made by e2fsck, but this is hardly problem of e2image itself.

So, please look at the patch, try it and let me know what else you thing is
useful to implement, or what would you like to change.

Anny comments appreciated.

Thanks!

-Lukas

             reply	other threads:[~2010-12-01 18:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 17:41 Lukas Czerner [this message]
2010-12-01 17:41 ` [PATCH] e2image: Add support for qcow2 format Lukas Czerner
2010-12-01 19:16 ` [PARCH 0/1 RFC] e2image: Add support for QCOW2 image format Amir Goldstein
2010-12-02  8:23   ` Lukas Czerner
2010-12-02 10:03     ` Amir Goldstein
2010-12-02 10:23       ` Lukas Czerner
2010-12-02 10:56         ` Amir Goldstein
2010-12-02 11:11           ` Lukas Czerner
2010-12-02 12:23             ` Amir Goldstein
2010-12-04  7:37               ` Amir Goldstein
2010-12-06 10:27                 ` Lukas Czerner
2010-12-01 22:52 ` Andreas Dilger
2010-12-02  8:24   ` Lukas Czerner

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=1291225309-10750-1-git-send-email-lczerner@redhat.com \
    --to=lczerner@redhat.com \
    --cc=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /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).