On 22.03.2010 02:13, Edward Ned Harvey wrote:
Actually ... Why should there be a ZFS property to share NFS, when you
can
already do that with "share" and "dfstab?" And still the zfs property
exists.
Probably because it is easy to create new filesystems and clone them;
as
NFS only works per filesystem you need to edit dfstab every time when
you
add a filesystem. With the nfs property, zfs create the NFS export,
etc.
Either I'm missing something, or you are.
If I export /somedir and then I create a new zfs filesystem /somedir/foo/bar
then I don't have to mess around with dfstab, because it's a subdirectory of
an exported directory, it's already accessible via NFS. So unless I
misunderstand what you're saying, you're wrong.
This is the only situation I can imagine, where you would want to create a
ZFS filesystem and have it default to NFS exported.
Actually, I can see some reasons for this. Some of us wants directories
mounted "the same place" at all servers. Consider the following:
zfs inherit sharenfs pool/nfs
zfs create -o mountpoint=/home pool/nfs/home
zfs create -o mountpoint=/webpages pool/nfs/www
zfs create -o mountpoint=/someotherdir pool/nfs/otherdir
etc.
So, I do see the point of the sharenfs attribute. ;)
//Svein
--
Sending mail from a temporary set up workstation, as my primary W500 is
off for service. PGP not installed.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
