Hi,
As Santhosh mentioned 3.5 support POSIX ACL configuration through NFS mount, i.e. setfacl and getfacl commands work through NFS mount.
As Santhosh mentioned 3.5 support POSIX ACL configuration through NFS mount, i.e. setfacl and getfacl commands work through NFS mount.
>
Also, can I do an in-place upgrade from 3.4 to 3.5 by just replacing the Gluster RPMs?
>
>
--Humble
On Tue, Jun 3, 2014 at 5:36 PM, Indivar Nair <indivar.nair@xxxxxxxxxxxx> wrote:
Indivar NairRegards,In my case, both setfacl and getfacl aren't working.Will this fix work in my case too?
Also, can I do an in-place upgrade from 3.4 to 3.5 by just replacing the Gluster RPMs?
On Tue, Jun 3, 2014 at 5:26 PM, Santosh Pradhan <spradhan@xxxxxxxxxx> wrote:
I guess Gluster 3.5 has fixed the NFS-ACL issues and getfacl/setfacl works there.
Regards,
Santosh
On 06/03/2014 05:10 PM, Indivar Nair wrote:
The getfacl or setfacl commands does not work on any dir/files on this mount.mount -t nfs -o vers=3,mountproto=tcp,acl <gluster_server>:/volume /mntBut it doesn't seem to be working.The main purpose of the upgrade was to get ACL Support on NFS exports.The OS is CentOS 6.3.It was a straight forward upgrade using Yum.Hi All,I recently upgraded a Gluster 3.3.1 installation to Gluster 3.4.
I mounted the gluster volume using the following options -
The plan is to re-export the NFS Mounts using Samba+CTDB.
NFS mounts seem to give better performance than Gluster Mounts.
Am I missing something?
Regards,
Indivar Nair
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users