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: Wed, 20 Apr 2016 16:38:19 +0200 [thread overview]
Message-ID: <nf848r$jfe$1@ger.gmane.org> (raw)
In-Reply-To: <20160420115036.GG6517@noname.str.redhat.com>
On 04/20/2016 01:50 PM, Kevin Wolf wrote:
> To catch all possible write failures, I think pwrite, pwritev and
> possibly fdatasync need to be considered.
I've now a
> strace -f -p 10727 -e trace=pwrite,pwritev,fdatasync,file -t 2>&1 | gzip -1 -c >trace.gz
attached to the qemu-process.
If the incident rate stays the same, by tomorrow I should be able
to correlate newly emitted I/O-errors in the guest with that log.
Regards,
Lutz Vieweg
next prev parent reply other threads:[~2016-04-20 14:38 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 [this message]
2016-04-21 15:54 ` Lutz Vieweg
2016-04-22 1:16 ` Fam Zheng
2016-04-22 10:47 ` Lutz Vieweg
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='nf848r$jfe$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 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).