Gluster VMs Paused State then not resumable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

I'm wondering if anyone's had any luck with running VMs on top of a gluster VM?
I have a bug open here,
https://bugzilla.redhat.com/show_bug.cgi?id=1058300 about VMs going
into a paused state and not being able to resume.

It's gone a little quiet, so I was wondering has anyone else had any
luck with this style of setup? I have my gluster and virt on the same
boxes, and currently 5 in the cluster (replica 2)

A few cases this can be reproduced:

- switch dies
- cable unplug
- gluster volume stop
- gluster brick dies

I recently tried a suggested volume option:
gluster volume set vm-data network.ping-timeout 10

The qemu logs now report on virsh resume vmname:
block I/O error in device 'drive-virtio-disk0': Transport endpoint is
not connected (107)

Thanks,
Andrew
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users




[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux