Hi, Thanks Niels, your hints about those two options did the trick although I had to enable both of them and I had to add nscd (sssd provides user identities) to this mix as well. Now back to the problem with ACL’s. Is your test setup something like this: GlusterFS 3.7.2 replicated volume on Centos/RHEL 7 and client or clients accessing GlusterFS volumes by NFS protocol, correct? # gluster volume info acltest Volume Name: acltest Type: Replicate Volume ID: 9e0de3f5-45ba-4612-a4f1-16bc5d1eb985 Status: Started Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: vfs-node-01:/data/gfs/acltest/brick0/brick Brick2: vfs-node-02:/data/gfs/acltest/brick0/brick Options Reconfigured: server.manage-gids: on nfs.server-aux-gids: on performance.readdir-ahead: on server.event-threads: 32 performance.cache-size: 2GB storage.linux-aio: on nfs.disable: off performance.write-behind-window-size: 1GB performance.nfs.io-cache: on performance.nfs.write-behind-window-size: 250MB performance.nfs.stat-prefetch: on performance.nfs.read-ahead: on performance.nfs.io-threads: on cluster.readdir-optimize: on network.remote-dio: on auth.allow: 10.1.1.32,10.1.1.42 diagnostics.latency-measurement: on diagnostics.count-fop-hits: on nfs.rpc-auth-allow: 10.1.1.32,10.1.1.42 nfs.trusted-sync: on Maybe there is a way to increase verbosity of nfs server which could help me to trace this problem. I did not find any good hints for increasing verbosity of nfs server in documentation. Regards, J. On 30 Jul 2015, at 10:09, Jiffin Tony Thottan <jthottan@xxxxxxxxxx> wrote:
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users