Hey gents,
I just want to know what the outlook is on more/better GlusterFS support in updated versions of Proxmox.
I've run into a few usability issues that basically make GlusterFS support almost unusable in Proxmox. For example, the simple creation of a QCOW2 image makes Proxmox timeout, and unable to continue. The reason is that the entire disk image (say 500GB image) is being written/created on the GlusterFS volume - which can take a really long time - and Proxmox's timeout is set incredibly short.
Why are Qcow2 images created on GlusterFS volumes 0% sparse and HUGE to start, but VMDK images are incredibly thin? Why does QCOW2 image creation take seconds on NFS/iSCSI but HOURS on GlusterFS?
Same with snapshot backups - if i want to restore a snapshot that contains a QCOW2 image, the restore fails/times out for the same reasons.
I can work around these issues, but my god is it making life miserable. Essentially, I have to restore the backup to an NFS share, then Move Disk to GlusterFS and change it from QCOW2 to VMDK, or else it fails.
I'm afraid to put this into production without the knowledge that better GlusterFS support will be coming.
Sam
I just want to know what the outlook is on more/better GlusterFS support in updated versions of Proxmox.
I've run into a few usability issues that basically make GlusterFS support almost unusable in Proxmox. For example, the simple creation of a QCOW2 image makes Proxmox timeout, and unable to continue. The reason is that the entire disk image (say 500GB image) is being written/created on the GlusterFS volume - which can take a really long time - and Proxmox's timeout is set incredibly short.
Why are Qcow2 images created on GlusterFS volumes 0% sparse and HUGE to start, but VMDK images are incredibly thin? Why does QCOW2 image creation take seconds on NFS/iSCSI but HOURS on GlusterFS?
Same with snapshot backups - if i want to restore a snapshot that contains a QCOW2 image, the restore fails/times out for the same reasons.
I can work around these issues, but my god is it making life miserable. Essentially, I have to restore the backup to an NFS share, then Move Disk to GlusterFS and change it from QCOW2 to VMDK, or else it fails.
I'm afraid to put this into production without the knowledge that better GlusterFS support will be coming.
Sam
Last edited: