Wonder if someone can point me in the right direction here - just built some new bricks running gluster 3.4 alpha 3 (from http://download.gluster.org) with the objective of testing them to replace some existing 3.2 systems in production. The main thing I was after was NFS ACL support, however on getting everything setup, I still don't seem to be able to see POSIX extended ACLs on the filesystem when mounted via NFS, they as ever show up fine when mounted via the gluster fuse client. I know NFS ACL support is on the feature list for 3.4, I'm wondering if it's not yet included in the alphas? Thanks! James Basic test output below: [jim at puppet testdir]$ sudo mount -t nfs -o nfsvers=3,acl webcontent:/ssl /tmp/nfs/ [jim at puppet testdir]$ sudo mount -t glusterfs -o acl webcontent:/ssl /tmp/gluster/ [jim at puppet testdir]$ ls -la /tmp/nfs/testdir/ total 8 drwxrwxr-x 2 root root 4096 May 4 00:50 . drwxr-xr-x 10 root root 4096 May 4 00:49 .. -rw-rwxr-- 1 root root 0 May 4 00:50 file1 -rw-r--r-- 1 root root 0 May 4 00:50 file2 -rw-r--r-- 1 root root 0 May 4 00:50 file3 [jim at puppet testdir]$ ls -la /tmp/gluster/testdir/ total 8 drwxrwxr-x+ 2 root root 4096 May 4 00:50 . drwxr-xr-x 10 root root 4096 May 4 00:49 .. -rw-rwxr--+ 1 root root 0 May 4 00:50 file1 -rw-r--r-- 1 root root 0 May 4 00:50 file2 -rw-r--r-- 1 root root 0 May 4 00:50 file3 [jim at puppet testdir]$ getfacl /tmp/nfs/testdir/file1 getfacl: /tmp/nfs/testdir/file1: Invalid argument [jim at puppet testdir]$ getfacl /tmp/gluster/testdir/file1 getfacl: Removing leading '/' from absolute path names # file: tmp/gluster/testdir/file1 # owner: root # group: root user::rw- group::r-- group:apache:rwx mask::rwx other::r--
