Re: Changes in NFS mounts from 14.3 to -CURRENT (almost 15)?

On Fri, Sep 12, 2025 at 7:55 PM Zaphod Beeblebrox <zbeeble@gmail.com> wrote:
>
> My overall goal is to have a FreeBSD workstation before Windows 10 dies.  That's coming up pretty quickly, so I've been testing.  Because FreeBSD's proton support is very much dependant on 15-CURRENT, I upgraded both the new workstation and my poudriere box to the 15-current about 2 weeks ago.
>
> Now... normally, when the workstation boots, half a dozen NFS mounts to the poudriere server (also fileserver) occur.  This has been the config since ... well... since back to FreeBSD 4 or so.
>
> My workstation's fstab has lines of the form:
>
> vr:/vr1/tmp /d/vr/tmp nfs rw,-3,-T,-l,-i,-b 0 0
>
> 'vr' being the hostname and so on.  On vr,
> [2:31:331]root@vr:~> zfs get sharenfs vr1/tmp
> NAME     PROPERTY  VALUE                    SOURCE
> vr1/tmp  sharenfs  -maproot=nobody ump run  local
>
> Now... for some number of upgrades, this spits out lines like "-i deprecated, use -o intr" ... which it still does --- but then it hangs ... for one NFS time out and it moves onto the next share.  No errors on either the client or the server.  What's changed here?  Both machines were working before the upgrade from 14.3 to 15-c.

Those options are from the Jurassic period, but they should still work, afaik.

I suspect your mount problem is something related to networking
(firewall or ipv4 vs ipv6 or ???). Note that NFSv3 does need rpcbind
to be working.

rick