From: Max Reitz <mreitz@redhat.com>
To: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, den@openvz.org, vsementsov@virtuozzo.com
Subject: Re: [Qemu-devel] [PATCH 0/2] qemu-img convert: ignore read errors
Date: Wed, 10 Apr 2019 17:26:42 +0200 [thread overview]
Message-ID: <6bd4c6e6-a7f1-99f4-c6bf-77099a49e4e1@redhat.com> (raw)
In-Reply-To: <1554821792-968307-1-git-send-email-andrey.shinkevich@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 473 bytes --]
On 09.04.19 16:56, Andrey Shinkevich wrote:
> The 'qemu-img convert' new command option 'force read' with the key '-R'
> allows converting a damaged image to get all the available information
> in case of the read errors. The program reports read errors and continue
> the image conversion. The users should keep in their minds that the
> resulting image is inconsistent.
I’ve already sent a series “Add salvaging mode to convert” back in December.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-04-10 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 14:56 [Qemu-devel] [PATCH 0/2] qemu-img convert: ignore read errors Andrey Shinkevich
2019-04-09 14:56 ` Andrey Shinkevich
2019-04-09 14:56 ` [Qemu-devel] [PATCH 1/2] " Andrey Shinkevich
2019-04-09 14:56 ` Andrey Shinkevich
2019-04-10 8:58 ` Vladimir Sementsov-Ogievskiy
2019-04-10 8:58 ` Vladimir Sementsov-Ogievskiy
2019-04-09 14:56 ` [Qemu-devel] [PATCH 2/2] iotests: new test 253 check qemu-img convert force read Andrey Shinkevich
2019-04-09 14:56 ` Andrey Shinkevich
2019-04-10 8:59 ` Vladimir Sementsov-Ogievskiy
2019-04-10 8:59 ` Vladimir Sementsov-Ogievskiy
2019-04-10 15:26 ` Max Reitz [this message]
2019-04-10 15:26 ` [Qemu-devel] [PATCH 0/2] qemu-img convert: ignore read errors 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=6bd4c6e6-a7f1-99f4-c6bf-77099a49e4e1@redhat.com \
--to=mreitz@redhat.com \
--cc=andrey.shinkevich@virtuozzo.com \
--cc=den@openvz.org \
--cc=kwolf@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).