As was recommended, I did this:
# pfexec chmod -R A=everyone@:rwxpdDaARWcCos:fd:allow /datapool
For good measure, I also made sure the Unix owner and group were correct:
# pfexec chown -R root:sysadmin /datapool
Just to verify:
# ls -ldV /datapool /datapool/test
drwxrwxrwx+ 8 root sysadmin 8 Nov 26 17:20 /datapool
everyone@:rwxpdDaARWcCos:fd-----:allow
drwxrwxrwx+ 4 root sysadmin 6 Nov 26 01:56 /datapool/test
everyone@:rwxpdDaARWcCos:fd-----:allow
Now, on the zpool itself (/datapool, shared as \\mune\media), I can read and
change permissions on the datapool main volume, and even create files and
directories directly on the share from Windows. I can also read and write to
the newly created subdirectories of the zpool. Also, if I use the individual
ZFS volume's share (\\mune\media_test, for example), I can read, write, change
permissions, etc.
However, there still remains a problem of being able to read or write to the
ZFS volumes, like datapool/test, through the datapool share (for instance,
\\mune\media\test). This appears to be a problem crossing from the main volume
(datapool) into the other ZFS volumes (datapool/test) on the pool.
Is there something else I need to look at to access, for example,
\\mune\media\test? ZFS properties tables perhaps? Does the CIFS server not
allow a user to cross ZFS volumes, even if the filesystem permissions allow it?
Thanks for the help so far! You guys rock.
Cheers,
Kevin
--
This message posted from opensolaris.org
_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
