From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
"open list:Block layer core" <qemu-block@nongnu.org>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH for-5.0? v3] qemu-img: Report convert errors by bytes, not sectors
Date: Thu, 2 Apr 2020 23:44:54 +0200 [thread overview]
Message-ID: <a0cc9691-22d1-d533-a66e-701524bb3628@redhat.com> (raw)
In-Reply-To: <20200402135717.476398-1-eblake@redhat.com>
On 4/2/20 3:57 PM, Eric Blake wrote:
> Various qemu-img commands are inconsistent on whether they report
> status/errors in terms of bytes or sector offsets. The latter is
> confusing (especially as more places move to 4k block sizes), so let's
> switch everything to just use bytes everywhere. One iotest is
> impacted.
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
>
> v3: Fix affected iotest [patchew]
>
> qemu-img.c | 8 ++++----
> tests/qemu-iotests/244.out | 2 +-
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/qemu-img.c b/qemu-img.c
> index b167376bd72e..821cbf610e5f 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -1924,8 +1924,8 @@ retry:
> if (status == BLK_DATA && !copy_range) {
> ret = convert_co_read(s, sector_num, n, buf);
> if (ret < 0) {
> - error_report("error while reading sector %" PRId64
> - ": %s", sector_num, strerror(-ret));
> + error_report("error while reading at byte %lld: %s",
> + sector_num * BDRV_SECTOR_SIZE, strerror(-ret));
> s->ret = ret;
> }
> } else if (!s->min_sparse && status == BLK_ZERO) {
> @@ -1953,8 +1953,8 @@ retry:
> ret = convert_co_write(s, sector_num, n, buf, status);
> }
> if (ret < 0) {
> - error_report("error while writing sector %" PRId64
> - ": %s", sector_num, strerror(-ret));
> + error_report("error while writing at byte %lld: %s",
> + sector_num * BDRV_SECTOR_SIZE, strerror(-ret));
> s->ret = ret;
> }
> }
> diff --git a/tests/qemu-iotests/244.out b/tests/qemu-iotests/244.out
> index e6f4dc79934b..56329deb4b9f 100644
> --- a/tests/qemu-iotests/244.out
> +++ b/tests/qemu-iotests/244.out
> @@ -33,7 +33,7 @@ Convert to compressed target with data file:
> Formatting 'TEST_DIR/t.IMGFMT.src', fmt=IMGFMT size=67108864
> wrote 1048576/1048576 bytes at offset 0
> 1 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> -qemu-img: error while writing sector 0: Operation not supported
> +qemu-img: error while writing at byte 0: Operation not supported
>
> Convert uncompressed, then write compressed data manually:
> Images are identical.
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2020-04-02 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 13:57 [PATCH for-5.0? v3] qemu-img: Report convert errors by bytes, not sectors Eric Blake
2020-04-02 21:44 ` Philippe Mathieu-Daudé [this message]
2020-04-03 9:56 ` 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=a0cc9691-22d1-d533-a66e-701524bb3628@redhat.com \
--to=philmd@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).