qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] qcow2: Avoid making the L1 table too big
Date: Tue, 5 Jul 2016 19:37:12 +0200	[thread overview]
Message-ID: <7bc2bb03-7244-ed8a-91fd-c94b1e3ebe0f@redhat.com> (raw)
In-Reply-To: <20160615153630.2116-1-mreitz@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 874 bytes --]

On 15.06.2016 17:36, Max Reitz wrote:
> See https://bugs.launchpad.net/qemu/+bug/1592590 for a bug report.
> 
> Reproducer:
> 
> $ ./qemu-img create -f qcow2 test.qcow2 1M
> Formatting 'test.qcow2', fmt=qcow2 size=1048576 encryption=off
> cluster_size=65536 lazy_refcounts=off refcount_bits=16
> $ ./qemu-img resize test.qcow2 100000T
> Image resized.
> $ ./qemu-img info test.qcow2
> qemu-img: Could not open 'test.qcow2': Active L1 table too large
> 
> After this series:
> 
> $ ./qemu-img resize test.qcow2 100000T
> qemu-img: Error resizing image: File too large
> 
> 
> Max Reitz (2):
>   qemu-img: Use strerror() for generic resize error
>   qcow2: Avoid making the L1 table too big
> 
>  block/qcow2-cluster.c | 2 +-
>  qemu-img.c            | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

Applied to my block branch.

Max


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 498 bytes --]

      parent reply	other threads:[~2016-07-05 17:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 15:36 [Qemu-devel] [PATCH 0/2] qcow2: Avoid making the L1 table too big Max Reitz
2016-06-15 15:36 ` [Qemu-devel] [PATCH 1/2] qemu-img: Use strerror() for generic resize error Max Reitz
2016-06-15 15:44   ` Eric Blake
2016-06-15 15:36 ` [Qemu-devel] [PATCH 2/2] qcow2: Avoid making the L1 table too big Max Reitz
2016-06-15 15:43   ` Eric Blake
2016-07-06  8:40   ` Kevin Wolf
2016-07-06 12:47     ` Max Reitz
2016-07-06 12:54       ` Kevin Wolf
2016-07-05 17:37 ` Max Reitz [this message]

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=7bc2bb03-7244-ed8a-91fd-c94b1e3ebe0f@redhat.com \
    --to=mreitz@redhat.com \
    --cc=kwolf@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).