From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, armbru@redhat.com,
eblake@redhat.com, xiechanglong.d@gmail.com,
wencongyang2@huawei.com, hreitz@redhat.com, jsnow@redhat.com,
f.ebner@proxmox.com
Subject: Re: [PATCH v4 5/5] iotests: add backup-discard-source
Date: Thu, 13 Jun 2024 10:02:26 +0200 [thread overview]
Message-ID: <ZmqnkubkBeVYhW7_@redhat.com> (raw)
In-Reply-To: <accc6cdc-7b1e-4d26-9352-380f93cc3853@yandex-team.ru>
Am 12.06.2024 um 21:21 hat Vladimir Sementsov-Ogievskiy geschrieben:
> On 11.06.24 20:49, Kevin Wolf wrote:
> > Am 13.03.2024 um 16:28 hat Vladimir Sementsov-Ogievskiy geschrieben:
> > > Add test for a new backup option: discard-source.
> > >
> > > Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
> > > Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
> > > Tested-by: Fiona Ebner <f.ebner@proxmox.com>
> >
> > This test fails for me, and it already does so after this commit that
> > introduced it. I haven't checked what get_actual_size(), but I'm running
> > on XFS, so its preallocation could be causing this. We generally avoid
> > checking the number of allocated blocks in image files for this reason.
> >
>
> Hmm right, I see that relying on allocated size is bad thing. Better
> is to check block status, to see how many qcow2 clusters are
> allocated.
>
> Do we have some qmp command to get such information? The simplest way
> I see is to add dirty to temp block-node, and then check its dirty
> count through query-named-block-nodes
Hm, does it have to be QMP in a running QEMU process? I'm not sure what
the best way would be there.
Otherwise, my approach would be 'qemu-img check' or even 'qemu-img map',
depending on what you want to verify with it.
Kevin
next prev parent reply other threads:[~2024-06-13 8:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 15:28 [PATCH v4 0/5] backup: discard-source parameter Vladimir Sementsov-Ogievskiy
2024-03-13 15:28 ` [PATCH v4 1/5] block/copy-before-write: fix permission Vladimir Sementsov-Ogievskiy
2024-03-13 15:28 ` [PATCH v4 2/5] block/copy-before-write: support unligned snapshot-discard Vladimir Sementsov-Ogievskiy
2024-03-13 15:28 ` [PATCH v4 3/5] block/copy-before-write: create block_copy bitmap in filter node Vladimir Sementsov-Ogievskiy
2024-03-13 15:28 ` [PATCH v4 4/5] qapi: blockdev-backup: add discard-source parameter Vladimir Sementsov-Ogievskiy
2024-03-13 16:08 ` Markus Armbruster
2024-03-14 13:44 ` Vladimir Sementsov-Ogievskiy
2024-03-13 15:28 ` [PATCH v4 5/5] iotests: add backup-discard-source Vladimir Sementsov-Ogievskiy
2024-06-11 17:49 ` Kevin Wolf
2024-06-12 19:21 ` Vladimir Sementsov-Ogievskiy
2024-06-13 8:02 ` Kevin Wolf [this message]
2024-06-20 14:15 ` Vladimir Sementsov-Ogievskiy
2024-04-05 13:46 ` [PATCH v4 0/5] backup: discard-source parameter Vladimir Sementsov-Ogievskiy
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=ZmqnkubkBeVYhW7_@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=f.ebner@proxmox.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
--cc=wencongyang2@huawei.com \
--cc=xiechanglong.d@gmail.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).