On Wed, Mar 19, 2008 at 12:02 PM, Laurent Blume <laurent at elanor.org> wrote: > Thanks. > I don't completely understand, though. I agree the error message might be > valid, but why does cp try to touch ACL in the first place? There are no ACL > whatsoever on those files. And yet, when doing "ls -l", all the files are > shown with a "+", like if there were. > > >
I too noticed this long ago, and have settled into living with "noacl" on linux clients. I believe its extended attributes that don't copy over NFS, but Solaris attempts to honor them in the writing of the files and updates the metadata stored concerning those files. In other words, you can copy files locally or remotely between linux and other UNIXen, but as soon as you copy to NFS/ZFS it doesn't store the correct attributes, but the files are flagged as if they do with the +. Any further file access will fail on those files. A cp triggers it during the copy itself. I feel I'll hear from the list that again Solaris is doing the correct thing, and every other client is broken, so I've not pushed this and just lived with noacl to prevent it. > Laurent > > > This message posted from opensolaris.org > _______________________________________________ > nfs-discuss mailing list > nfs-discuss at opensolaris.org >
