Actually the correct way to DISABLE nfs on gluster volume is:
gluster volume set <VOLNAME> nfs.disable on
Setting nfs.disable to off, actually enables gluster nfs (it sounds a bit counter intuitive I have to admit)
Thank you for the reply Fabian, the thing is gluster worked just fine under OpenVZ (I am using also proxmox version 3.x), does it downgrade performance that much that lxc support on top of glusterfs can not be implemented?
Ok, it seems that for the template error issue the fix is to replace line 1067 from /usr/share/perl5/PVE/API2/Nodes.pm
if !($scfg->{type} eq 'dir' || $scfg->{type} eq 'nfs');
with:
if !($scfg->{type} eq 'dir' || $scfg->{type} eq 'nfs' || $scfg->{type} eq 'glusterfs');
Will try now to fix the...
Hello guys, I encounter the following issues when creating a Container or trying to download an LXC template on top of glusterfs volume.
The error messages are as follows:
- when trying to create a container: "TASK ERROR: unable to create containers on storage type 'glusterfs'"
- when trying to...
Thank you very much for your replies. I always performed the echo 3 > /proc/sys/vm/drop_caches, so the tests you saw were "real" sync speed. I wanted to use a real file with actual content, not something with zeros - transfer speed proved to be ~30% higher when transferring a "zero" file over...
Hi guys, I'm planning to move everything from SolusVM to Proxmox, due to the fact that SolusVM does not support HA.
Everything went fine until I ended up testing GlusterFS as shared storage, I'm using replication over 3 nodes and when I started creating containers I noticed that the process was...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.