From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: nsoffer@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH for-5.1 2/2] iotests: Test sparseness for qemu-img convert -n
Date: Tue, 21 Jul 2020 13:25:41 +0200 [thread overview]
Message-ID: <00954f0b-10e0-cae9-3f9c-66d79a38fb3f@redhat.com> (raw)
In-Reply-To: <20200721112028.GA18481@linux.fritz.box>
[-- Attachment #1.1: Type: text/plain, Size: 1773 bytes --]
On 21.07.20 13:20, Kevin Wolf wrote:
> Am 21.07.2020 um 12:19 hat Max Reitz geschrieben:
>> On 20.07.20 15:18, Kevin Wolf wrote:
>>> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
>>> ---
>>> tests/qemu-iotests/122 | 34 ++++++++++++++++++++++++++++++++++
>>> tests/qemu-iotests/122.out | 17 +++++++++++++++++
>>> 2 files changed, 51 insertions(+)
>>>
>>> diff --git a/tests/qemu-iotests/122 b/tests/qemu-iotests/122
>>> index dfd1cd05d6..1112fc0730 100755
>>> --- a/tests/qemu-iotests/122
>>> +++ b/tests/qemu-iotests/122
>>> @@ -281,6 +281,40 @@ $QEMU_IMG convert -O $IMGFMT -n "$TEST_IMG" "$TEST_IMG".orig
>>>
>>> $QEMU_IMG compare "$TEST_IMG" "$TEST_IMG".orig
>>>
>>> +echo
>>> +echo '=== -n to an empty image ==='
>>> +echo
>>> +
>>> +_make_test_img 64M
>>> +
>>> +# Convert with -n, which should not result in a fully allocated image, not even
>>> +# with compat=0.10 (because the target doesn't have a backing file)
>>> +TEST_IMG="$TEST_IMG".orig _make_test_img -o compat=1.1 64M
>>> +$QEMU_IMG convert -O $IMGFMT -n "$TEST_IMG" "$TEST_IMG".orig
>>> +$QEMU_IMG map --output=json "$TEST_IMG".orig
>>> +
>>> +TEST_IMG="$TEST_IMG".orig _make_test_img -o compat=0.10 64M
>>
>> It’s a shame that with this, the test will no longer pass with
>> refcount_bits=1. (Or an external data file.)
>
> You mean because of the compat=0.10? We already use that in this test
> case, however just with "$QEMU_IMG convert" so that $IMGOPTS doesn't
> apply.
>
> I guess I could just override $IMGOPTS for this line to get the same
> behaviour here and make sure that none of these options are used.
Well... Not my favorite, but probably because I just never thought of that.
I suppose it works, so why not, actually.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-07-21 11:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 13:18 [PATCH for-5.1 0/2] qemu-img convert -n: Keep qcow2 v2 target sparse Kevin Wolf
2020-07-20 13:18 ` [PATCH for-5.1 1/2] qcow2: Implement v2 zero writes with discard if possible Kevin Wolf
2020-07-20 14:50 ` Nir Soffer
2020-07-21 10:07 ` Max Reitz
2020-07-22 17:01 ` Maxim Levitsky
2020-07-22 17:14 ` Kevin Wolf
2020-07-22 17:15 ` Maxim Levitsky
2020-07-20 13:18 ` [PATCH for-5.1 2/2] iotests: Test sparseness for qemu-img convert -n Kevin Wolf
2020-07-20 14:47 ` Nir Soffer
2020-07-21 13:49 ` Kevin Wolf
2020-07-21 10:19 ` Max Reitz
2020-07-21 11:20 ` Kevin Wolf
2020-07-21 11:25 ` 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=00954f0b-10e0-cae9-3f9c-66d79a38fb3f@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=nsoffer@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).