From: Kevin Wolf <kwolf@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [RFC 0/2]: QMP DISK_ERROR event
Date: Tue, 02 Feb 2010 10:25:19 +0100 [thread overview]
Message-ID: <4B67EF7F.8060308@redhat.com> (raw)
In-Reply-To: <1265047668-15039-1-git-send-email-lcapitulino@redhat.com>
Hi Luiz,
Am 01.02.2010 19:07, schrieb Luiz Capitulino:
> Hi there,
>
> I've been requested by libvirt guys to add a QMP event for disk I/O errors,
> this is what this series is about.
>
> It's a RFC because I need feedback on the following:
>
> 1. drive_get_on_error() is called on all disk errors, right?
Well, yes, it is for all devices that support rerror/werror. But it also
might be called in other situations. Look at the "get" in the function
name, it's really a getter function and not a event handler.
> 2. I've tested only ENOSPC errors, is there a way to test other errors? Like
> read ones?
So you'll probably want some EIO. Some recent bugs I've been handling
were a about images on NFS when the NFS server want away. It's a
reliable way to get EIO (mount with -osoft and small timeouts). I guess
qemu-nbd and the nbd: protocol might work, too.
Or maybe copy the start of a qcow2 image to a too small device.
> 3. Is this the right approach at all? :)
Yes and no. As I said above, drive_get_on_error() is not the right place
to do it. Unfortunately it looks like there isn't a single generic place
where it can be done, but the call to the event handler must be added to
every device.
Kevin
next prev parent reply other threads:[~2010-02-02 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 18:07 [Qemu-devel] [RFC 0/2]: QMP DISK_ERROR event Luiz Capitulino
2010-02-01 18:07 ` [Qemu-devel] [PATCH 1/2] block: Introduce drive_get_err_action() Luiz Capitulino
2010-02-01 18:07 ` [Qemu-devel] [PATCH 2/2] QMP: Introduce DISK_ERROR event Luiz Capitulino
2010-02-02 9:30 ` [Qemu-devel] " Kevin Wolf
2010-02-02 9:25 ` Kevin Wolf [this message]
2010-02-02 12:17 ` [Qemu-devel] Re: [RFC 0/2]: QMP " Luiz Capitulino
2010-02-02 12:19 ` Kevin Wolf
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=4B67EF7F.8060308@redhat.com \
--to=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).