Did someone already get this issue ? Can it be kernel related ? I am using
a Centos 7.2 image from my cloud provider, could it be a low level
configuration that is missing ?
2016-12-29 18:19 GMT+01:00 vincent gromakowski <
vincent.gromakow...@gmail.com>:
> Hi all,
> Any idea regarding the log
Hi all,
Any idea regarding the log outputs ?
What are the ACL to set on bricks directory or gluster brick root ?
2016-12-28 11:25 GMT+01:00 vincent gromakowski <
vincent.gromakow...@gmail.com>:
> Hi,
> Please find below the outputs. I previse that I can read and write to the
> volume but only
Hi,
Please find below the outputs. I previse that I can read and write to the
volume but only with "sudo" or root account whatever the ACL or the
ownership I set on fuse directories (even 777)
*>sudo gluster peer status*
*Number of Peers: 3*
*Hostname: bd-reactive-worker-4*
*Uuid:
On 12/28/2016 02:42 PM, vincent gromakowski wrote:
Hi,
Can someone help me solve this issue ? I am really stuck on it and I
don't find any workaround...
Thanks a lot.
V
Hi,
What does gluster volume status show? I think it is because of
quorum you are not able to read / write to and
Hi,
Can someone help me solve this issue ? I am really stuck on it and I don't
find any workaround...
Thanks a lot.
V
2016-12-26 15:02 GMT+01:00 vincent gromakowski <
vincent.gromakow...@gmail.com>:
> Hi all,
> I am currently setting a gluster volume on 4 Centos 7.2 nodes. Everything
> seems to
Hi all,
I am currently setting a gluster volume on 4 Centos 7.2 nodes. Everything
seems to be OK from the volume creation to the fuse mounting but after that
I can't access data (read or write) without a sudo even if I set 777
permissions.
I have checked that permissions on underlying FS (an XFS
