On Wed, 20 Jan 2016 12:34:02 +0100
Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote:
> On 20/01/2016 06:08, Roman Mamedov wrote:
> > I don't get any ENOSPC errors on the host, also it doesn't seem to
> > be a slowdown caused by disk I/O searching for free space, just a
> > complete lock-up: I monitor the guest with 'ping', and when it
> > happens, the ping responses stop immediately and do not return,
> > also there is no reaction to any keypress in the KVM VNC window.
>
> Can you go to the QEMU monitor (Ctrl-Alt-F2 typically, or just add
> "-monitor stdio" to the QEMU command line) and type "info status"?
Aha, now this is getting somewhere.
------------------
(qemu) info status
VM status: paused (io-error)
(qemu) info block
hd: vm.img (raw)
I/O status: nospace
Detect zeroes: unmap
ide1-cd0: [not inserted]
Removable device: not locked, tray closed
floppy0: [not inserted]
Removable device: not locked, tray closed
sd0: [not inserted]
Removable device: not locked, tray closed
(qemu) info block-jobs
No active jobs
------------------
So this seems to be an transient ENOSPC error returned to the data writing
process by the FS during snapshotting. I can now reproduce this without KVM,
just with dd. Seems not much to do with KVM then, I will post more details to
the btrfs list. Thanks!
--
With respect,
Roman
Attachment:
signature.asc
Description: PGP signature
