Support for gluster 3.8

U

Ulrar

Active Member
Feb 4, 2016
37
1
28
34
Hi,

Since 3.7.11 isn't really usable for storing VMs due to a nasty corruption bug in sharded volumes, I was waiting for either 3.7.12 or 3.8.
3.8 came out yesterday, but looks like proxmox isn't compatible, when can we expect an update to make that work ?

For now, adding the volume is a bit wonky, looks like it can't detect the volume name by itself but if I type it by hand I can click next and add it fine. Then it takes a while to actually mark it as "active", but it does finally detect the correct size for it. Then when adding VMs on the volume, it just gets stuck for a while on the creationg task and ends up throwing an error :

Jun 16 15:39:36 s2.name pvedaemon[5688]: create failed - unable to create image: got lock timeout - aborting command

Thanks !
 
  • Like
Reactions: chrone
Ulrar said:
Hi,

Since 3.7.11 isn't really usable for storing VMs due to a nasty corruption bug in sharded volumes, I was waiting for either 3.7.12 or 3.8.
3.8 came out yesterday, but looks like proxmox isn't compatible, when can we expect an update to make that work ?
Click to expand...

usually not the day after an upstream release ;)

For now, adding the volume is a bit wonky, looks like it can't detect the volume name by itself but if I type it by hand I can click next and add it fine. Then it takes a while to actually mark it as "active", but it does finally detect the correct size for it. Then when adding VMs on the volume, it just gets stuck for a while on the creationg task and ends up throwing an error :

Jun 16 15:39:36 s2.name pvedaemon[5688]: create failed - unable to create image: got lock timeout - aborting command

Thanks !
Click to expand...

if you experience issues on the proxmox side of things (the gluster packages themselves are not built/maintained/provided by us), please file a bug report at bugzilla.proxmox.com and include all the relevant information (i.e., output of "pveversion -v", storage and vm/lxc configurations, complete list of steps you did, any and all error messages you encountered, system logs, ...)
 
  • Like
Reactions: chrone
Sure, I release it'll take some time, just wondering if you had any idea how much.
I guess the main problem isn't proxmox, it might be qemu. Although I suppose the menu to add the storage is developed by proxmox ?
 
Hi All,

glusterfs 3.8 runs fine on my PVE 4.2 with ZFS storage. Below is my setup and package info

Code: 
root@pve239:/mnt/pve# pveversion -v
proxmox-ve: 4.2-54 (running kernel: 4.4.10-1-pve)
pve-manager: 4.2-14 (running version: 4.2-14/655f944a)
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.8-1-pve: 4.4.8-52
pve-kernel-4.4.10-1-pve: 4.4.10-54
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-42
qemu-server: 4.0-80
pve-firmware: 1.1-8
libpve-common-perl: 4.0-68
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-54
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-19
pve-container: 1.0-68
pve-firewall: 2.0-29
pve-ha-manager: 1.0-31
ksm-control-daemon: 1.2-1
glusterfs-client: 3.8.0-1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie
openvswitch-switch: 2.5.0-1
root@pve239:/mnt/pve# dpkg -l |grep gluster
ii  glusterfs-client               3.8.0-1                        amd64        clustered file-system (client package)
ii  glusterfs-common               3.8.0-1                        amd64        GlusterFS common libraries and translator modules
ii  glusterfs-server               3.8.0-1                        amd64        clustered file-system (server package)
 
Ulrar said:
Hi,

Since 3.7.11 isn't really usable for storing VMs due to a nasty corruption bug in sharded volumes, I was waiting for either 3.7.12 or 3.8.
3.8 came out yesterday, but looks like proxmox isn't compatible, when can we expect an update to make that work ?

For now, adding the volume is a bit wonky, looks like it can't detect the volume name by itself but if I type it by hand I can click next and add it fine. Then it takes a while to actually mark it as "active", but it does finally detect the correct size for it. Then when adding VMs on the volume, it just gets stuck for a while on the creationg task and ends up throwing an error :

Jun 16 15:39:36 s2.name pvedaemon[5688]: create failed - unable to create image: got lock timeout - aborting command

Thanks !
Click to expand...
I have the same issue,I already update to lastest version of proxomox,the issue is still there.I have three nodes cluster,2 replicatoin with 1 arbiter volume,shard enabled.
My proxmox version info
root@pvee:~# pveversion -v
proxmox-ve: 4.2-54 (running kernel: 4.4.10-1-pve)
pve-manager: 4.2-15 (running version: 4.2-15/6669ad2c)
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.8-1-pve: 4.4.8-52
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.4.10-1-pve: 4.4.10-54
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-42
qemu-server: 4.0-81
pve-firmware: 1.1-8
libpve-common-perl: 4.0-68
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-55
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-19
pve-container: 1.0-68
pve-firewall: 2.0-29
pve-ha-manager: 1.0-32
ksm-control-daemon: 1.2-1
glusterfs-client: 3.8.0-1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie
ceph: 0.94.3-1jessie
 
You must log in or register to reply here.
Top Bottom