From: Lutz Vieweg <lvml@5t9.de>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org
Subject: Re: [Qemu-devel] I/O errors reported to guest for raw-image-file backed /dev/vda - but host sees no I/O errors
Date: Fri, 22 Apr 2016 12:47:32 +0200 [thread overview]
Message-ID: <nfcvg4$uh$1@ger.gmane.org> (raw)
In-Reply-To: <nfat48$9u1$1@ger.gmane.org>
On 04/21/2016 05:54 PM, Lutz Vieweg wrote:
> And indeed, the errors occured exactly at the time a backup procedure
> was preparing a read-only snapshot with "btrfs subvolume snapshot -r" -
> so until I can upgrade to a mainline kernel including the fix, I'll
> pause the qemu process while the "btrfs subvolume snapshot -r" runs.
Alas, this seems not to be sufficient to get rid of the symptom easily -
I guess that some of the "pwrite"s are executed asynchronously, at
a time when the qemu emulation is already in "pause" mode.
Will retry with some safeguard sleep time between the "stop" to
the monitor and the creation of the snapshot.
Regards,
Lutz Vieweg
prev parent reply other threads:[~2016-04-22 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 17:47 [Qemu-devel] I/O errors reported to guest for raw-image-file backed /dev/vda - but host sees no I/O errors Lutz Vieweg
2016-04-20 2:11 ` Fam Zheng
2016-04-20 11:50 ` Kevin Wolf
2016-04-20 14:38 ` Lutz Vieweg
2016-04-21 15:54 ` Lutz Vieweg
2016-04-22 1:16 ` Fam Zheng
2016-04-22 10:47 ` Lutz Vieweg [this message]
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='nfcvg4$uh$1@ger.gmane.org' \
--to=lvml@5t9.de \
--cc=qemu-block@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.