I quickly checked on VFS FSAL using below EXPORT block. I see same issue on
vfs fsal also. Any suggestion here please ?
*Operation to request attribute not supported.Failed to instantiate ACL.*
EXPORT
{
Export_Id = 77;
# Exported path (mandatory)
Path = /home;
# Pseudo Path (required for NFS v4)
Pseudo = /home;
# Required for access (default is None)
# Could use CLIENT blocks instead
Access_Type = RW;
Disable_ACL = FALSE;
NFS_Protocols = 4;
Squash = no_root_squash;
# Exporting FSAL
FSAL {
Name = VFS;
}
}
Thanks,
Sagar.
On Fri, Feb 16, 2018 at 2:25 PM, Sagar M D <sagar...@gmail.com> wrote:
> Supriti,
>
> We are testing our own FSAL.
>
> Thanks,
> Sagar.
>
>
> On Fri, Feb 16, 2018 at 2:15 PM, Supriti Singh <supriti.si...@suse.com>
> wrote:
>
>> Hi Sagar,
>>
>> Which FSAL are you using?
>>
>>
>>
>>
>> ------
>> Supriti Singh
>> SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
>> HRB 21284 (AG Nürnberg)
>>
>> >>> Sagar M D <sagar...@gmail.com> 02/16/18 9:15 AM >>>
>> Hi,
>>
>> We are setting below value in our EXPORT block to enable ACL.
>> *Disable_ACL = FALSE;*
>>
>> However when try to do any ACL operation it throws get below error:-
>>
>> *Operation to request attribute not supported.Failed to instantiate ACL.*
>>
>> On further analysis, i found that getattr call on our fsal export's root
>> folder is returning 3 (ALLOW | DENY) in aclsupport field. But getattr call
>> on pseudo export is returning "0" in aclsupport field.
>>
>>
>> Is there anything else in fsal to be taken care to enable acls ?
>>
>> Thanks,
>> Sagar.
>>
>>
>>
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
