ZFS + NFS + multiple hosts/mount options ..?

Willem Jan Withagen wjw at digiware.nl
Tue Aug 30 17:40:45 UTC 2016


On 30-8-2016 18:46, Lev Serebryakov wrote:
> On 30.08.2016 18:31, Willem Jan Withagen wrote:
> 
>>>> Is there a way through the zfs set sharenfs="..." property to share
>>>> data/somefs readonly to host "dev.lan" _and_ read/write to host 
>>>> "duvel.prod.lan" ? Or should I just set sharenfs="off" and use
>>>> /etc/exports (I'm using NFS4) ? It seems impossible to have multiple
>>>> hosts/options/... when the sharenfs property is used ..
>>>  No luck here. I've raised this question multiple times withoput any
>>> reaction. Here is (very old) PRs with patch, which implements this:
>>>
>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=147881
>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202820
>>>
>>
>> I'd say, forget about getting any flexible through sharenfs.
>   WHY?!
> 
>> Did that discussion about 3 years ago, and it boiled down. Don't dare to
>   I don't see any good reason to not support this, aside "It will not be
> compatible with Illumos". I don't buy this, sorry. Any other reasons?
> 
>> change it because the people doing ZFS don't like it.
>  There is one BIG problem: deep ZFS hierarchies. If I need to export 100
> FSes (100 users' home directories, for example) in one ZFS tree to 4
> networks (2xIPv4, 2xIPv6) I need to add 400 (!!!) lines to /etc/exports
> by hands. All these lines will be virtually the same, and good luck to
> maintain this mess.
> 
>  If "sharenfs" supports multiple hosts/networks, I need to set this
> property ONCE (on zpool/home, parent of all FSes in question) and IT'S
> ALL! And if I need to change same options, I need to change it ONCE and
> re-export ZFS.
> 
>  Unfortunately, it is NOT enough to export parent FS :(

Hi Lev,

I agree with you

More or less the arguments I had at that time.
(though I don't have that many FSes.)

And I gave up. Perhaps that tells more about me than anything else.
The discussion I tried to have was cut short with the argument that it
would not go in because  upstream would not like it, or would not want
in the version I submitted.

But please do feel free and get something in that would please more.

--WjW




More information about the freebsd-fs mailing list