FreeNAS 9.1.1, ldap bound to OS X 10.5.8 Open Directory.
I've 4 zpools.
3 have datasets defined, one dataset per zpool.
All 4 zpools are exported NFS and AFP.
The AFP mounts seem to be fine - read/write to zpools from AFP clients functions.
NFS client read/write to the zpool without dataset works as expected. Unix ownership and permissions on the zpool share and its subdirectories are functional and accurate.
Authorized NFS clients can mount the zpools with datasets.
- But ownership and permissions of the datasets are not accurate; their ownerships are changed to root:wheel and permissions changed to 755.
- client 'ls' listing of zpool root shows the dataset directory listing with incorrect ownership/permissions, but client 'ls' listing of dataset content is empty and with no ls command error.
Why do I see this behavior for datasets? And why do I see it only for NFS shares?
Thanks,
-Neil
I've 4 zpools.
3 have datasets defined, one dataset per zpool.
All 4 zpools are exported NFS and AFP.
The AFP mounts seem to be fine - read/write to zpools from AFP clients functions.
NFS client read/write to the zpool without dataset works as expected. Unix ownership and permissions on the zpool share and its subdirectories are functional and accurate.
Authorized NFS clients can mount the zpools with datasets.
- But ownership and permissions of the datasets are not accurate; their ownerships are changed to root:wheel and permissions changed to 755.
- client 'ls' listing of zpool root shows the dataset directory listing with incorrect ownership/permissions, but client 'ls' listing of dataset content is empty and with no ls command error.
Why do I see this behavior for datasets? And why do I see it only for NFS shares?
Thanks,
-Neil
