From: Paolo Bonzini <pbonzini@redhat.com>
To: Kuniyasu Suzaki <k.suzaki@aist.go.jp>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] delvm does not reduce the qcow2 file size
Date: Mon, 15 Oct 2012 15:25:16 +0200 [thread overview]
Message-ID: <507C0EBC.3030805@redhat.com> (raw)
In-Reply-To: <20121015.183337.17413021.k.suzaki@aist.go.jp>
Il 15/10/2012 11:33, Kuniyasu Suzaki ha scritto:
> Hello,
>
> "delvm" is a command to delete a snapshot image in a qcow2 file.
> However it does not reduce the qcow2 file size.
Note that the file will not grow when new allocations are performed in
the future.
QEMU should also convert the unused clusters to "holes" in the file
system, but it doesn't do that yet.
> Is there any method to reduce the qcow2 file size when I delete a snapshot image?
> should I "convert" the qcow2 file?
I'm not sure what convert does if you have internal snapshots.
Paolo
next prev parent reply other threads:[~2012-10-15 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 9:33 [Qemu-devel] delvm does not reduce the qcow2 file size Kuniyasu Suzaki
2012-10-15 13:25 ` Paolo Bonzini [this message]
2012-10-15 14:24 ` Kevin Wolf
2012-10-16 6:23 ` Kuniyasu Suzaki
2012-10-16 6:54 ` Paolo Bonzini
2012-10-16 11:06 ` Kuniyasu Suzaki
2012-10-16 11:19 ` Paolo Bonzini
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=507C0EBC.3030805@redhat.com \
--to=pbonzini@redhat.com \
--cc=k.suzaki@aist.go.jp \
--cc=qemu-devel@nongnu.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).