Unable to set ACLs on ZFS file system over NFSv4?

[Andrew Leonard]

On Thu, May 10, 2012 at 2:23 PM, Rick Macklem <rmacklem at uoguelph.ca> wrote:

> I wrote:

>> If you capture a packet trace from before you do the NFSv4 mount, I
>> can
>> take a look and see what the server is saying. (Basically, at mount
>> time
>> a reply to a Getattr should including the supported attributes and
>> that
>> should include the ACL bit. Then the setfacl becomes a Setattr of the
>> ACL
>> attribute.)
>> # tcpdump -s 0 -w acl.pcap host <server>
>> - run on the client should do it
>>
>> If you want to look at it, use wireshark. If you want me to look, just
>> email acl.pcap as an attachment.
>>
>> rick
>> ps: Although I suspect it is the server that isn't behaving, please
>> use
>> the FreeBSD client for the above.
>> pss: I've cc'd trasz@ in case he can spot some reason why it wouldn't
>> work.
>>
> Oh, and make sure "user1" isn't in more than 16 groups, because that is the
> limit for AUTH_SYS. (I'm not sure what the effect of user1 being in more
> than 16 groups would be, but might as well eliminate it as a cause.)

Thanks, Rick - I'll send the pcap over private email, as I'm sure
$DAYJOB would consider it somewhat sensitive.

Looking in wireshark, if I'm reading it correctly, I don't see
anything for FATTR4_ACL in any replies.  On the final connection, I do
see NFS4ERR_IO set as the status for the reply to the setattr - but
from Googling, my understanding is that response is supposed to
indicate a hard error, such as a hardware problem.

Also, I have verified that "user1" is not a member of more than 16
groups, so we can rule that out - that user is in only three groups.

-Andy