From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Eyal Shenitzky <eshenitz@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [PATCH] qemu-img: Support bitmap --merge into backing image
Date: Fri, 11 Sep 2020 10:31:19 +0200 [thread overview]
Message-ID: <32a96bcc-78de-a13e-c090-ad00c3b4c4ad@redhat.com> (raw)
In-Reply-To: <20200909123358.1244744-1-eblake@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 2214 bytes --]
On 09.09.20 14:33, Eric Blake wrote:
> If you have the chain 'base.qcow2 <- top.qcow2' and want to merge a
> bitmap from top into base, qemu-img was failing with:
>
> qemu-img: Could not open 'top.qcow2': Could not open backing file: Failed to get shared "write" lock
> Is another process using the image [base.qcow2]?
>
> The easiest fix is to not open the entire backing chain of the source
> image, so that we aren't worrying about competing BDS visiting the
> backing image as both a read-only backing of the source and the
> writeable destination.
>
> Fixes: http://bugzilla.redhat.com/1877209
> Reported-by: Eyal Shenitzky <eshenitz@redhat.com>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
> qemu-img.c | 3 +-
> tests/qemu-iotests/291 | 12 ++++++++
> tests/qemu-iotests/291.out | 56 ++++++++++++++++++++++++++++++++++++++
> 3 files changed, 70 insertions(+), 1 deletion(-)
>
> diff --git a/qemu-img.c b/qemu-img.c
> index eb2fc1f86243..b15098a2f9b3 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -4755,7 +4755,8 @@ static int img_bitmap(int argc, char **argv)
> }
> bs = blk_bs(blk);
> if (src_filename) {
> - src = img_open(false, src_filename, src_fmt, 0, false, false, false);
> + src = img_open(false, src_filename, src_fmt, BDRV_O_NO_BACKING,
> + false, false, false);
Why not do the same for the destination BB?
> if (!src) {
> goto out;
> }
> diff --git a/tests/qemu-iotests/291 b/tests/qemu-iotests/291
> index 1e0bb76959bb..4f837b205655 100755
> --- a/tests/qemu-iotests/291
> +++ b/tests/qemu-iotests/291
[...]
> @@ -107,6 +116,9 @@ $QEMU_IMG map --output=json --image-opts \
> nbd_server_start_unix_socket -r -f qcow2 -B b2 "$TEST_IMG"
> $QEMU_IMG map --output=json --image-opts \
> "$IMG,x-dirty-bitmap=qemu:dirty-bitmap:b2" | _filter_qemu_img_map
> +nbd_server_start_unix_socket -r -f qcow2 -B b3 "$TEST_IMG"
Why not look into $TEST_IMG.base to see specifically whether the bitmap
is there?
(I also am quite surprised that it’s even possible to export bitmaps
from backing nodes, but, well.)
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-11 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 12:33 [PATCH] qemu-img: Support bitmap --merge into backing image Eric Blake
2020-09-11 8:31 ` Max Reitz [this message]
2020-09-11 15:17 ` Eric Blake
2020-09-14 9:35 ` Max Reitz
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=32a96bcc-78de-a13e-c090-ad00c3b4c4ad@redhat.com \
--to=mreitz@redhat.com \
--cc=eblake@redhat.com \
--cc=eshenitz@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).