You've created two zfs filesystems outer and inner.
# zfs create -o casesensitivity=insensitive tank/outer
# zfs create -o casesensitivity=insensitive tank/outer/inner
inner is defined as a zfs filesystem, it is not just a simple directory in
outer, it is a filesystem and it is a ZFS file system hierarchy.
ZFS File System Hierarchy
A ZFS storage pool is a logical collection of devices that
provide space for datasets. A storage pool is also the root
of the ZFS file system hierarchy.
The root of the pool can be accessed as a file system,
including mounting and unmounting, taking snapshots, and
setting properties. The physical storage characteristics,
however, are managed by the zpool(1M) command.
See zpool(1M) for more information on creating and adminis-
tering pools.
If you'd set a mountpoint, for instance:
# zfs set mountpoint=/export/home tank/outer
it would be inherited by the child.
Then you shared outer, but not inner.
# zfs sharesmb=name=outer tank/outer
# zfs sharesmb=off tank/outer/inner
So inner is not a share and therefor not accessible. The property of tank/outer
is not inherited by tank/outer/inner, because you explicitly "unshared" it (
zfs share is not possible ) and properties may not inherited from the ancestor
( see man zfs inherit ).
As far as I know, a file system with sharesmb property set to "off" can be
managed through share(1M), unshare(1M), and dfstab(4).
If the property is set to "on" it is automatically shared or unshared with zfs
share and zfs unshare commands.
And finally, if you change the property sharesmb the share and all children
inheriting the property are reshared, except that ones that are set to "off".
So the filesystem inner is not a share !
see and check man zfs(1M)
regards,
claudia
--
This message posted from opensolaris.org
_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
