Using NFSv4 ACL
You should have already followed the directions on the using nfsv4 and preceding pages (though note krb5 is optional).
Note that NFSv4 ACLs are more fine-grained than the POSIX ACLs supported by local linux filesystems. You can type "nfs4_getfacl" to get a list of what all the mask bits mean.
Linux servers, and Solaris servers exporting UFS (as opposed to the newer ZFS) only support a subset of NFSv4 ACLs corresponding to POSIX ACLs. Newer linux servers will accept any NFSv4 ACL, and automatically convert it to a (possibly more restrictive) POSIX ACL, but Solaris and older linux servers may reject the ACL outright.
To help with such servers, and to provide a POSIX ACL interface for those more familiar with it, we also provide patches to the POSIX ACL tools which can set and get "POSIX" ACLs by transparently translating them to and from NFSv4 ACLs.
NFSv4-aware POSIX ACL tools
The POSIX<->NFSv4 translation performed by these patches is complex, so we recommend using the native NFSv4 ACL tools described above, unless (for the reasons described above) you are sure you need NFSv4-aware versions of the POSIX ACL tools:
See the getfacl and setfacl man pages for more documentation. Note that these utilities do not provide access to the underlying NFSv4 ACLs; instead, they translate between NFSv4 ACLs and the more coarse-grained linux-native "POSIX" ACLs, using a mapping described in this internet draft.
Direct access to underlying NFSv4 ACLs is provided by the nfs4_getfacl and nfs4_setfacl commands described in the previous section.