Re: zfs sharenfs oddness

From: Daniel Kalchev <daniel_at_digsys.bg>
Date: Wed, 25 Jun 2025 14:16:00 UTC
You don't set it to on and something else at the same time. Your 
sequence has the effect of just doing

zfs set sharenfs="maproot=root -alldirs -network 192.168.1.10/32" 
data/testvdev

setting it first to "on" is not neccesary and prefixing the exports line 
with "on," is wrong.

Daniel

On 25.06.25 г. 17:10 ч., void wrote:
> Hi,
>
> zfs-2.3.99-31-FreeBSD_gb2f6de7b5
> zfs-kmod-2.3.99-31-FreeBSD_gb2f6de7b5
> FreeBSD 15.0-CURRENT #0 main-n273486-88dd0550920 GENERIC-NODEBUG amd64 
> 1500026 1500026
>
> In order to get sharenfs to work, I have to do the following on the 
> server
>
> # zfs set sharenfs=on data/testvdev
> # zfs set sharenfs="maproot=root -alldirs -network 192.168.1.10/32" 
> data/testvdev
>
> and then run the usual 'service mountd restart'
>
> The below doesn't work, and by that I mean i cannot get it to mount 
> from the client on .10
>
> # zfs set sharenfs="on,maproot=root -alldirs -network 192.168.1.10/32" 
> data/testvdev
>
> Setting the sharenfs property to 'on' has to happen by itself before 
> it'll
> work.
>
> Why is this, and is there a better workaround?