From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>, Alberto Garcia <berto@igalia.com>,
qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, kwolf@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 2/5] qcow2: Document some maximum size constraints
Date: Wed, 18 Apr 2018 08:49:55 -0500 [thread overview]
Message-ID: <5430e92a-db1e-e853-e7d8-1b31cbfc0edc@redhat.com> (raw)
In-Reply-To: <f1d1c403-1a2a-aee2-5fe6-7cfbb81339d6@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]
On 04/13/2018 12:08 PM, Max Reitz wrote:
>>>> With 512 byte clusters and 64 bit refcount entries I still get 8 PB,
>>>> way over what's limited by the L1/L2 tables (128 GB).
>>>
>>> Do I need to make any modifications to the sentence, then?
>>
>> I guess what surprised me the first time that I read it was that it
>> suggests that this has to be taken into account when calculating the
>> physical limits of an image, while in practice it can be ignored.
>>
>> You could say something like
>>
>> Although the larger the cluster size, the larger the offsets that can
>> be covered by the refcount table, in practice these limits cannot be
>> reached because they are larger than the ones imposed by other data
>> structures.
>
> Are there any updates here? I guess I personally would just drop the
> whole paragraph, because I think it really doesn't matter...
Yeah, I need to post a v5 of this series now that 2.13 is nearly open.
>
> Also note that the maximum file size of ext4 is 16 PB (for 4 kB blocks).
> OK, it's bigger for XFS, but that still gives some perspective.
>
> Also, long before anyone is going to complain about the specification
> failing to mention that limit, they are going to complain that qemu
> refuses to open their image (because of its limit on the reftable size).
>
> Max
>
>> although I'm sure that you can come up with a better wording than mine :)
>>
>> Berto
>>
>
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2018-04-18 13:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 15:55 [Qemu-devel] [PATCH v4 0/5] minor compression improvements Eric Blake
2018-02-27 16:29 ` [Qemu-devel] [PATCH v4 1/5] qcow2: Prefer byte-based calls into bs->file Eric Blake
2018-02-27 16:29 ` [Qemu-devel] [PATCH v4 2/5] qcow2: Document some maximum size constraints Eric Blake
2018-02-28 10:26 ` Alberto Garcia
2018-02-28 14:01 ` Eric Blake
2018-02-28 14:20 ` Alberto Garcia
2018-04-13 17:08 ` Max Reitz
2018-04-18 13:49 ` Eric Blake [this message]
2018-02-27 16:29 ` [Qemu-devel] [PATCH v4 3/5] qcow2: Reduce REFT_OFFSET_MASK Eric Blake
2018-02-28 12:18 ` Alberto Garcia
2018-02-27 16:29 ` [Qemu-devel] [PATCH v4 4/5] qcow2: Don't allow overflow during cluster allocation Eric Blake
2018-02-27 16:29 ` [Qemu-devel] [PATCH v4 5/5] qcow2: Avoid memory over-allocation on compressed images Eric Blake
2018-02-28 14:22 ` Alberto Garcia
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=5430e92a-db1e-e853-e7d8-1b31cbfc0edc@redhat.com \
--to=eblake@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).