zfs discuss - Apr 2006 - Re: [osol-discuss] However, the zfs file system /export/zfs_0 must be shared ?? What ?

On 4/12/06, Darren J Moffat <Darren.Moffat at sun.com>
wrote:
> So why not have /export/zfs_0/
>                 /export/zfs_0/jumpstart
>                 /export/zfs_0/jumpstart/s10
>                 /export/zfs_0/jumpstart/s10/SXCRb35
>
> all as separate ZFS filesystems, they are cheap after all :-)
It is still a bug which should be fixed. The requirement that only the
base of a ZFS file system can be shared is a serious limitation which
will hamper or even prevent deployment of ZFS at large sites.
Simplified example: Someone may want to set up shares temporarily in a
sub directory and the requirement to create an extra ZFS file system
for that is a overkill, if not even a risk for production usage (I
consider changes in a file system setup as a far higher risk than
letting people share their data via NFS).

Holger

On Mon, Apr 17, 2006 at 09:41:21PM +0200, Holger Berger
wrote:
> 
> It is still a bug which should be fixed. The requirement that only the
> base of a ZFS file system can be shared is a serious limitation which
> will hamper or even prevent deployment of ZFS at large sites.
I haven''t quite grokked the original thread completely, but the above
statement isn''t true.  You can _always_ use /etc/dfs/dfstab to share
whatever directories you want.  The "zfs set sharenfs=XXX" syntax is
just a simplified interface for managing shares, and has the beneficial
side effect that such options are kept with your data (in the case of
import/export, for example).  There will always be things you may want
to do (such as sharing it under a different name, or sharing
subdirectories of a filesystem) which will exceed the capabilities of
this simplified interface.

Hope that helps,

- Eric

--
Eric Schrock, Solaris Kernel Development       http://blogs.sun.com/eschrock