[Gluster-users] setfacl: Operation not supported

[Jiffin Tony Thottan]

On 28/06/16 19:12, Evans, Kyle wrote:
> Hi Jiffin,
>
> Thanks for confirming that it is a bug and it is fixed in a newer 
> version; I appreciate it.
>

no problem

>
> Kyle
>
>
>
> From: Jiffin Tony Thottan
> Date: Tuesday, June 28, 2016 at 4:53 AM
> To: Kyle Evans, "gluster-users at gluster.org 
> <mailto:gluster-users at gluster.org>"
> Subject: Re: [Gluster-users] setfacl: Operation not supported
>
> Hi Evans,
>
> Sorry for the delayed reply.
>
> I tried to reproduce on my setup(version 3.7.9) and it was working 
> fine for me.
> But it was fairly reproducible with version which you had mentioned. I 
> don't know
> which patch got fixed that issue, still I suggest to update your 
> gluster so that both
> issues mentioned below will be solved
>
> On 24/06/16 23:43, Evans, Kyle wrote:
>>
>> 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]
>>
>>
>
> Ignore this , this is spurious message which was fixed by this patch 
> http://review.gluster.org/#/c/13452/
>
> --
>
> Regards
>>
>>
>> Thanks,
>>
>>
>> Kyle
>>
>>
>> From: Jiffin Tony Thottan
>> Date: Friday, June 24, 2016 at 2:17 AM
>> To: Kyle Evans, "gluster-users at gluster.org"
>> Subject: Re: [Gluster-users] setfacl: Operation not supported
>>
>>
>>
>> On 24/06/16 02:08, Evans, Kyle wrote:
>>> I'm using gluster 3.7.5-19 on RHEL 7.2  Gluster periodically stops 
>>> allowing ACLs.  I have it configured in fstab like this:
>>>
>>> Server.example.com:/dir /mnt glusterfs defaults,_netdev,acl 0 0
>>>
>>>
>>> Also, the bricks are XFS.
>>>
>>> It usually works fine, but sometimes after a reboot, one of the 
>>> nodes won't allow acl operations like setfacl and getfacl.  They 
>>> give the error "Operation not supported".
>>>
>> 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
>>
>>> Sometimes it's not even after a reboot; it just stops supporting it.
>>>
>>> If I unmount and remount, it starts working again.  Does anybody 
>>> have any insight?
>>>
>>> Thanks,
>>>
>>> Kyle
>>>
>>>
>>> _______________________________________________
>>> Gluster-users mailing list
>>> Gluster-users at gluster.orghttp://www.gluster.org/mailman/listinfo/gluster-users
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160628/3ad6f304/attachment.html>