Our new-to-us Isilon is handling NFSv4 ACLs differently than other NFS
file servers we've had. In particular, something causes an 'O' to pop
up in the permission field, but I cannot find any documentation of it.
For example,
[Linux]$ nfs4_getfacl TODO
A::OWNER@:tTcCy
A::GROUP@:tcy
A::EVERYONE@:rwaxtTnNcy
A:O:OWNER@:rwadxtTnNcCoy
A:gO:admins@xxxxxxxxxx:rwadxtTnNcy
A:gO:readonly@madboa:rxtnc
A:O:EVERYONE@:tncy
I'll note that when those 'O' perms get added, our OmniOS
(Solaris-alike) hosts cannot read the ACLs:
[SunOS]$ ls -v TODO
ls: can't read ACL on TODO: Invalid argument
-rwxrwx--- 1 heinlein wheel 2488 Oct 2 15:13 TODO
If, on the Linux side, I run nfs4_editfacl and do nothing but remove
the 'O' permission symbols, then things clear up.
Has anyone here seen anything like this? My google-fu has failed.
--
Paul Heinlein
heinlein@xxxxxxxxxx
45°38' N, 122°6' W
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
