We recently upgraded all our nodes to pve 3.3, kernel 2.6.32-33-pve which upgraded our qemu to 2.1.2. However, I was pleased to see that in proxmox 3.3 roadmap that qemu 2.1.0 (now 2.1.2) was compiled over the glusterfs 3.5.2 libraries. So until recently I was operating on the pve test 2.1.0 version of qemu so that gluster worked properly (including live migration). Somebody had same problem or is able to tell me what could be happened and if i can increase the timeout?Ī while back I worked with people on this forum and we eventually got a version of qemu 2.1.0 compiled over glusterfs version 3.5.2. PV UUID 9OddA2-JuOq-kC2v-lnmg-md7l-7Xr3-Ii6xi0 I've free space on disk and the NFS target is working fine, i've just made a backup test for an other vps and it worked fine. I'm running backups in suspend mode for my vps from 1 year without problems, but this morning the vps was still suspended and the error message was:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |