car...@taltos.org said: > NetApp does _not_ expose an ACL via NFSv3, just old school POSIX mode/owner/ > group info. I don't know how NetApp deals with chmod, but I'm sure it's > documented.
The answer is, "It depends." If the NetApp volume is NTFS-only permissions, then chmod from the Unix/NFS side doesn't work, and you can only manipulate permissions from Windows clients.. If it's a "mixed" security-style volume, chmod from the Unix/NFS side will delete the NTFS ACL's, and the SMB clients will see faked-up ACL's that match the new POSIX permissions. Whichever side made the most recent change will be in effect. Newer OnTAP versions have an optional setting which overrides this effect of chmod if NFSv4 is in effect on mixed-security volumes, and instead tries to mirror the ACL's as identically as possible to both kinds of clients. Poor old NFSv3 and older clients still see gibberish POSIX permissions, but the least privilege available in ACL's is enforced by the filer. BTW, our experience has been that NFSv4 on NetApp does not work very well, and NetApp support folks have advised us to not use it in order to avoid crashing the filer. They of course blame the various incompatible NFSv4 client implementations out there.... Regards, Marion _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
