From: Kevin Wolf <kwolf@redhat.com>
To: Bug 322602 <322602@bugs.launchpad.net>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 322602] Re: Snapshot usage makes qcow2 image unusable due to large tables
Date: Fri, 11 Jun 2010 11:34:09 +0200 [thread overview]
Message-ID: <4C120311.8080406@redhat.com> (raw)
In-Reply-To: <20100611075959.13068.85161.malone@soybean.canonical.com>
Am 11.06.2010 09:59, schrieb Jes Sorensen:
> Could you please let us know whether this is still a problem and if it
> isn't, lets close this bug.
This looks like a purely hypothetical thing - have you seen this happen
in reality, and if so, with how many snapshots?
This is reported against a very old version, so we have to assume 4k
clusters. This means that a refcount block holds the refcounts for 4k /
2 = 2k clusters. Let's assume a refcount table of only one cluster, so
we can describe (4k / 8) * 2k = 1M clusters with this, which makes up an
image size of 4G.
To hold a 20G virtual disk plus some metadata we'll therefore need
something like 6 clusters = 24k. To make the refcount table consume just
1 MB, you'll therefore need at least 42 snapshots, each fully allocated
on its own, consuming 1 TB for the image. I doubt that there are too
many machines which can handle a 1 TB image file on disk, but not a 1 MB
refcount table in RAM.
Nowadays, of course, we're using 64k clusters by default. With a
refcount table of 64k we describe 16 TB there, with a 1 MB refcount
table it's 256 TB.
Kevin
next prev parent reply other threads:[~2010-06-11 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090129032712.7039.50315.malonedeb@gandwana.canonical.com>
2010-06-11 7:59 ` [Qemu-devel] [Bug 322602] Re: Snapshot usage makes qcow2 image unusable due to large tables Jes Sorensen
2010-06-11 9:34 ` Kevin Wolf [this message]
2016-11-04 15:39 ` Thomas Huth
2017-01-04 4:17 ` Launchpad Bug Tracker
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=4C120311.8080406@redhat.com \
--to=kwolf@redhat.com \
--cc=322602@bugs.launchpad.net \
--cc=Jes.Sorensen@redhat.com \
--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).