From: Fam Zheng <famz@redhat.com>
To: Bin Wu <wu.wubin@huawei.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
"pbonzini@redhat.com >> Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [question] block: do we have any consideration about adding retry support in error handling?
Date: Thu, 25 Dec 2014 10:42:32 +0800 [thread overview]
Message-ID: <20141225024232.GA6064@ad.nay.redhat.com> (raw)
In-Reply-To: <549B6EFA.3010603@huawei.com>
On Thu, 12/25 09:57, Bin Wu wrote:
> Hi,
>
> When IO error happens in physical device, qemu block layer supports error
> reporting, error ignoring and error stoping(for example, virtio-blk). Can we
> have any way to resend the error IO?
With error stop, the request is retried after resume.
Fam
next prev parent reply other threads:[~2014-12-25 2:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-25 1:57 [Qemu-devel] [question] block: do we have any consideration about adding retry support in error handling? Bin Wu
2014-12-25 2:42 ` Fam Zheng [this message]
2014-12-25 3:46 ` Bin Wu
2014-12-25 7:19 ` Fam Zheng
2014-12-25 9:19 ` Bin Wu
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=20141225024232.GA6064@ad.nay.redhat.com \
--to=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wu.wubin@huawei.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).