Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Oct 2009 01:15:35 +0000
From:      Kris Kennaway <kris@FreeBSD.org>
To:        "Arno J. Klaassen" <arno@heho.snv.jussieu.fr>
Cc:        freebsd-net@freebsd.org, Larry Rosenman <ler@lerctr.org>
Subject:   Re: ZFS and 'traditional' nfs-export
Message-ID:  <4AE79B37.5010203@FreeBSD.org>
In-Reply-To: <wpmy3cikj2.fsf@heho.snv.jussieu.fr>
References:  <wpbpjtwwg7.fsf@heho.snv.jussieu.fr>	<00b301ca5739$8e9b3850$abd1a8f0$@org> <wpmy3cikj2.fsf@heho.snv.jussieu.fr>

next in thread | previous in thread | raw e-mail | index | archive | help
Arno J. Klaassen wrote:
> hello,
> 
> "Larry Rosenman" <ler@lerctr.org> writes:
> 
>> ZFS makes its own version of the exports file.
>>
>> Just do it that way, and be safe.
>>
>> You can pass the full set of NFS options in the sharenfs parameter....
> 
> ah ok, I see. Thanks for answering.
> 
> I got fooled by the man zfs(1M) example :
> 
>  zfs set sharenfs='rw=@123.123.0.0/16,root=neo' tank/home
> 
> This syntax does not seem to work for me (8.0RC2).
> Maybe an extra line could be added that one can just set
> the sharenfs property to exactly the same character string
> as in /etc/exports.

Yeah that is the solaris notation -- various things in the manpages have 
not yet been customized for FreeBSD, which can be a bit confusing.

The only limitation I've found in using sharenfs is that you can't 
specify multiple exports for the same filesystem, e.g. exporting to 
different hosts/networks with different options.  The solaris notation 
above allows you to express this.

Kris




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AE79B37.5010203>