[Bugs] [Bug 1058300] VMs do not resume after paused state and storage connection to a gluster domain (they will also fail to be manually resumed)

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1058300



--- Comment #44 from Christopher Pereira <kripper at gmail.com> ---
No. False alarm.

It seems that lsof is not always returning the correct path.
Lsof's FAQ says "3.1.2    Why does lsof report the wrong path names?"

Additional info:

1) When stopping and resuming the gluster volume, it is also not possible to
resume the VM via virsh (libvirt).
In libvirt/qemu/VM logs, I get a:
block I/O error in device 'drive-virtio-disk0': Transport endpoint is not
connected (107)

2) If the VM is suspended in oVirt before stopping and resuming the gluster
volume, it can be resumed via oVirt.

3) If the VM is suspended in virsh before stopping and resuming the gluster
volume, it can be resumed via virsh.

Maybe the file descriptors pointing to the gluster volume must be reopened
after restarting the gluster volume.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.