From: Philipp Hahn <hahn@univention.de>
To: day knight <back2games@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: qcow2 eating up space when formattng Centos
Date: Fri, 28 Oct 2011 07:47:55 +0200 [thread overview]
Message-ID: <201110280748.00007.hahn@univention.de> (raw)
In-Reply-To: <CAHaoJrJfYgtAw2rA7yHmzxf3n9CqaVJk1n6=2+-UMNVdW_rCJQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
Hello Anonnymous, cc:kvm
On Friday 28 October 2011 04:48:57 day knight wrote:
> I am using ext3 and your explaination makes sense. May I also ask if
> the qcow image automatically adjusts to the size or is it ever
> expanding image?
That depends: Originally Qcow2 only expands, since Qemu/kvm doesn't know
what's inside your image file, that is if and what file systems it contains
and how they're structured. Because of that it can't know which blocks are
free and which are still used.
Since qemu/kvm-0.15 there is TRIM support (which originally was developed for
flash-storage media), which — I think — is also supported for Qcow2. If your
Guest-OS supports TRIM, it can tell the underlaying storage media — Qcow2 —
that blocks are now unused, which Qemu/kvm can then free.
> I mean lets say I have 100 Gig and write 20 Gig on
> qcow ext3 image and then delete 10 Gig data. Would it show up as
> 120Gig or 110 once the deletion is done
Sincerely
Philipp
--
Philipp Hahn Open Source Software Engineer hahn@univention.de
Univention GmbH Linux for Your Business fon: +49 421 22 232- 0
Mary-Somerville-Str.1 D-28359 Bremen fax: +49 421 22 232-99
http://www.univention.de/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2011-10-28 5:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 1:22 qcow2 eating up space when formattng Centos day knight
2011-10-24 7:17 ` Philipp Hahn
[not found] ` <CAHaoJrJfYgtAw2rA7yHmzxf3n9CqaVJk1n6=2+-UMNVdW_rCJQ@mail.gmail.com>
2011-10-28 5:47 ` Philipp Hahn [this message]
2011-10-28 20:05 ` day knight
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=201110280748.00007.hahn@univention.de \
--to=hahn@univention.de \
--cc=back2games@gmail.com \
--cc=kvm@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).