qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org,  Stefan Hajnoczi <stefanha@redhat.com>,
	 Kevin Wolf <kwolf@redhat.com>,  Hanna Reitz <hreitz@redhat.com>,
	 "open list:Block layer core" <qemu-block@nongnu.org>
Subject: Re: [PULL 13/14] tests: Add iotest mirror-sparse for recent patches
Date: Wed, 28 May 2025 18:23:58 +0200	[thread overview]
Message-ID: <87plfsya8x.fsf@pond.sub.org> (raw)
In-Reply-To: <5o7qspgmmjktoah6yoq5zp4uemhyultohiswqwvib7dqbh53ez@2ctslprvuxxx> (Eric Blake's message of "Wed, 28 May 2025 10:40:07 -0500")

Eric Blake <eblake@redhat.com> writes:

> On Wed, May 28, 2025 at 01:39:25PM +0200, Markus Armbruster wrote:
>> Eric Blake <eblake@redhat.com> writes:
>> 
>> > Prove that blockdev-mirror can now result in sparse raw destination
>> > files, regardless of whether the source is raw or qcow2.  By making
>> > this a separate test, it was possible to test effects of individual
>> > patches for the various pieces that all have to work together for a
>> > sparse mirror to be successful.
>> >
>
>> Fails for me:
>> 
>>     TAP version 13
>>     # QEMU          -- "/work/armbru/qemu/bld/qemu-system-x86_64" -nodefaults -display none -accel qtest
>>     # QEMU_IMG      -- "/work/armbru/qemu/bld/qemu-img" 
>>     # QEMU_IO       -- "/work/armbru/qemu/bld/qemu-io" --cache writeback --aio threads -f qcow2
>>     # QEMU_NBD      -- "/work/armbru/qemu/bld/qemu-nbd" 
>>     # IMGFMT        -- qcow2
>>     # IMGPROTO      -- file
>>     # PLATFORM      -- Linux/x86_64 dusky 6.12.7-200.fc41.x86_64
>>     # TEST_DIR      -- /work/armbru/qemu/bld-x86/scratch
>
> Which filesystem is TEST_DIR on?

$ findmnt --target /work/armbru/qemu/bld-x86/scratch
TARGET SOURCE                                     FSTYPE OPTIONS
/work  /dev/mapper/luks-898519e7-f64e-4a69-8cf9-8532063d8bb9
                                                  xfs    rw,relatime,seclabel,at

[...]



  reply	other threads:[~2025-05-28 16:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15  2:28 [PULL 00/14] NBD patches for 2025-05-14 Eric Blake
2025-05-15  2:28 ` [PULL 01/14] block: Expand block status mode from bool to flags Eric Blake
2025-05-15  2:28 ` [PULL 02/14] file-posix, gluster: Handle zero block status hint better Eric Blake
2025-05-15  2:28 ` [PULL 03/14] block: Let bdrv_co_is_zero_fast consolidate adjacent extents Eric Blake
2025-05-15  2:28 ` [PULL 04/14] block: Add new bdrv_co_is_all_zeroes() function Eric Blake
2025-05-15  2:28 ` [PULL 05/14] iotests: Improve iotest 194 to mirror data Eric Blake
2025-05-15  2:28 ` [PULL 06/14] mirror: Minor refactoring Eric Blake
2025-05-15  2:28 ` [PULL 07/14] mirror: Pass full sync mode rather than bool to internals Eric Blake
2025-05-15  2:28 ` [PULL 08/14] mirror: Allow QMP override to declare target already zero Eric Blake
2025-05-15  2:28 ` [PULL 09/14] mirror: Drop redundant zero_target parameter Eric Blake
2025-05-15  2:28 ` [PULL 10/14] mirror: Skip pre-zeroing destination if it is already zero Eric Blake
2025-05-15  2:28 ` [PULL 11/14] mirror: Skip writing zeroes when target " Eric Blake
2025-05-15  2:28 ` [PULL 12/14] iotests/common.rc: add disk_usage function Eric Blake
2025-05-15  2:28 ` [PULL 13/14] tests: Add iotest mirror-sparse for recent patches Eric Blake
2025-05-21  9:54   ` Fiona Ebner
2025-05-21 15:32     ` Eric Blake
2025-05-22  7:30       ` Fiona Ebner
2025-05-28 11:39   ` Markus Armbruster
2025-05-28 12:40     ` Eric Blake
2025-05-28 13:27       ` Markus Armbruster
2025-05-28 15:40     ` Eric Blake
2025-05-28 16:23       ` Markus Armbruster [this message]
2025-05-28 18:22         ` Eric Blake
2025-05-15  2:28 ` [PULL 14/14] mirror: Reduce I/O when destination is detect-zeroes:unmap Eric Blake
2025-05-15 21:53 ` [PULL 00/14] NBD patches for 2025-05-14 Stefan Hajnoczi

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=87plfsya8x.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).