-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I have not seen that with the fuse client. I had it happen repeatedly
when we were using gluster/NFS for /var/lib/nova/instances and/or
/var/lib/nova/instances/_base. The access to instances-XX/disk
(or its qcow2 backing image) would hang compl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I get around the problem on our gluster clusters by putting
"nobootwait" and/or "noauto" in my fstab and then having rc.local run
the mount command for the gluster mount points. Do not know if that is
more or less elegant then your workaround. It at
Having an odd problem on a new test environment we are setting up for a
partner. And not sure where to look next to figure out the problem or
really understand what the dht_layout_dir_mismatch INFO message is
telling me.
I was turning up a 4 node distributed volume, each brick is its own
19TB e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Howdy,
We need to re-ip the servers that make up a gluster volume.
Unfortunately when they were setup I was stupid and did not use
hostnames and instead specified each brick in the volume by ip. Ex
10.103.114.4:/exports/DATA 10.103.114.5:/exports
Howdy,
I was looking over the latest release of gluster and saw
https://github.com/gluster/glusterfs/blob/master/doc/authentication.txt
in the repo and saw the lines about username and password auth. Is
there any docs explaining how authentication works or is setup. I
failed at finding anything
