Greetings,
I have a working 3 nodes proxmox cluster.
Using glusterfs as storage without problem (created a manual mount point + a shared directory.)
Proxmox and glusterfs share the same nodes.
Now i would like to use libgfapi and get rid of fuse overhead, but it can't get it to work..
I added a storage type "glusterfs" in proxmox ui, but i always get a timeout while trying to create a vm.
TASK ERROR: create failed - unable to create image: got lock timeout - aborting command
It seems the qemu process will stay there forever :
root 42228 1 0 11:59 ? 00:00:00 /usr/bin/qemu-img create -f raw gluster://proxmoxt-rrgfs/glusterstorage/images/117/vm-117-disk-1.raw 2097152K
I had the same problem when using the command qemu-img info :
root@proxmoxt1:~# qemu-img info gluster://proxmoxt-rrgfs:24007/glusterstorage/images/101/vm-101-disk-1.raw 2>/dev/null
image: gluster://proxmoxt-rrgfs:24007/glusterstorage/images/101/vm-101-disk-1.raw
file format: raw
virtual size: 56G (60129542144 bytes)
disk size: 6.0G
It works fine when i add port 24007, but process hangs without it.
I tried a strace on glusterd process, and it won't receive anything when the port is not explicitly forced to 24007.
Is this the normal behaviour ? Is there a workaround to force the port used by proxmox ?
root@proxmoxt1:~# dpkg -l| grep gluster
ii glusterfs-client 3.5.1-1 amd64 clustered file-system (client package)
ii glusterfs-common 3.5.1-1 amd64 GlusterFS common libraries and translator modules
ii glusterfs-server 3.5.1-1 amd64 clustered file-system (server package)
root@proxmoxt1:~# pveversion -v
proxmox-ve-2.6.32: not correctly installed (running kernel: 3.10.0-3-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-3.10.0-3-pve: 3.10.0-11
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-18
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.1-1
Regards,
Alexandre.
I have a working 3 nodes proxmox cluster.
Using glusterfs as storage without problem (created a manual mount point + a shared directory.)
Proxmox and glusterfs share the same nodes.
Now i would like to use libgfapi and get rid of fuse overhead, but it can't get it to work..
I added a storage type "glusterfs" in proxmox ui, but i always get a timeout while trying to create a vm.
TASK ERROR: create failed - unable to create image: got lock timeout - aborting command
It seems the qemu process will stay there forever :
root 42228 1 0 11:59 ? 00:00:00 /usr/bin/qemu-img create -f raw gluster://proxmoxt-rrgfs/glusterstorage/images/117/vm-117-disk-1.raw 2097152K
I had the same problem when using the command qemu-img info :
root@proxmoxt1:~# qemu-img info gluster://proxmoxt-rrgfs:24007/glusterstorage/images/101/vm-101-disk-1.raw 2>/dev/null
image: gluster://proxmoxt-rrgfs:24007/glusterstorage/images/101/vm-101-disk-1.raw
file format: raw
virtual size: 56G (60129542144 bytes)
disk size: 6.0G
It works fine when i add port 24007, but process hangs without it.
I tried a strace on glusterd process, and it won't receive anything when the port is not explicitly forced to 24007.
Is this the normal behaviour ? Is there a workaround to force the port used by proxmox ?
root@proxmoxt1:~# dpkg -l| grep gluster
ii glusterfs-client 3.5.1-1 amd64 clustered file-system (client package)
ii glusterfs-common 3.5.1-1 amd64 GlusterFS common libraries and translator modules
ii glusterfs-server 3.5.1-1 amd64 clustered file-system (server package)
root@proxmoxt1:~# pveversion -v
proxmox-ve-2.6.32: not correctly installed (running kernel: 3.10.0-3-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-3.10.0-3-pve: 3.10.0-11
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-18
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.1-1
Regards,
Alexandre.