Trying to use a ZFS based profile directory (Vista x64), however saving the profile always fails (and reading as well as long as the 'check profile owner' policy is not disabled). Directories are created (even if there is no coerresponding entry in the logs) but contain *.tmp of size 0 only. ... log level = 1 acls:10 vfs:10 registry:10 auth:10 [profiles] comment = Roaming Profiles path = /export/profiles browsable = no read only = no create mask = 0600 directory mask = 0700 csc policy = disable guest ok = no printable = no hide files = /desktop.ini/outlook*.lnk/*Briefcase*/ # zfs stuff vfs objects = zfsacl full_audit vfs_full_audit:success = all vfs_full_audit:failure = all full_audit:facility = LOCAL1 full_audit:priority = NOTICE nfs4: mode = special nfs4: chown = true nfs4: acedup = merge zfsacl: acesort = ntfs inherit acls = Yes blocking locks = No delete readonly = Yes dos filetime resolution = Yes Tried this with the zfs order patch (see bug 5653) and without it - no luck. If I chmod 1777 to the parent directory and use 'inherit permissions' profile reading and writing works without any Win errors (however having 1777 on each file/dir is not, what anybody wants), which leads to the conclusion, that there is something wrong with the zfs/nfs stack ... log files are available from the URL above.
fixed in 3.3.1 (nfs4_acls.c directory check). see #6133