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
