Hi Jiffin,
Thanks for the help. You understand correctly, I am talking about the client. The problem is intermittent, and those lines DO appear in the log when it works but DO NOT appear in the log when it is broken. Also, here is another log I am getting that may be relevant:
[2016-06-13 17:39:33.128941] I [dict.c:473:dict_get] (-->/usr/lib64/glusterfs/3.7.5/xlator/system/posix-acl.so(posix_acl_setxattr_cbk+0x26) [0x7effdbdfb3a6] -->/usr/lib64/glusterfs/3.7.5/xlator/system/posix-acl.so(handling_other_acl_related_xattr+0x22) [0x7effdbdfb2a2] -->/lib64/libglusterfs.so.0(dict_get+0xac) [0x7effef3e80cc] ) 0-dict: !this || key=system.posix_acl_access [Invalid argument]
Thanks,
Kyle
From: Jiffin Tony Thottan
Date: Friday, June 24, 2016 at 2:17 AM To: Kyle Evans, "gluster-users@xxxxxxxxxxx" Subject: Re: [Gluster-users] setfacl: Operation not supported
On 24/06/16 02:08, Evans, Kyle wrote:
Did u meant client reboot ? Correct me if I am wrong, You have mounted the glusterfs volume with acl enabled and configured in fstab When you reboot client, acl operations are returning error as "Operation not supported". Can please follow the steps if possible after mounting can check the client log (in your example it should be /var/log/glusterfs/mnt.log) and confirm whether following block is present in the vol graph "volume posix-acl-autoload type system/posix-acl subvolumes dir end-volume" Clear the log file before reboot and just check whether same block is present after reboot -- Jiffin
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users