cp --preserve=xattr has the same system.nfs4_acl lines but lacks the
system.posix_acl_access lines and the fchmod.
A chmod / fchmod shouldn't clear the acl, it should only disable the permissions
not allowed by the mode. IIRC Solaris has some weird configuration knobs for
those kinds of things though.
That was my reading of acl(5) on solaris, but it doesn't seem to be
what's actually happening. (At least on openindiana.)
That would be a misbehavior / misconfiguration; --preserve=xattr should affect
non-permission xattrs only. Which attributes are permissions and which
are not is
configured in /etc/xattr.conf.
Well, I can confirm that if system.nfs4_acl is configured as
"permissions" in /etc/xattr.conf that cp ignores it entirely. So if the
almost-desired behavior was a side effect, then I guess this whole thing
is stuck in the old controversy about whether the acl library should
support nfs4 acls?