Re: zfs sharenfs woes

On Tue, Jul 22, 2025 at 08:16:27AM -0700, Rick Macklem wrote:

>Yea, baffling. The only recent change to mountd went in on May 1. If your
>mountd binary pre-dated that when it still worked, you could try reverting
>68daa78 and rebuilding mountd. (You don't need to do a full make buildworld,
>you can just...
># cd /urs/src/usr.sbin/mountd
># make SRCTOP=/usr/src
># cd /usr/obj/.../mountd ("..." is for a bunch of subdirs)
># mv /usr/sbin/mount /usr/sbin/mountd.new
># cp mountd /usr/sbin
># service mountd restart
>
>I don't see how 68daa78 could break this, but???

I think somehow the os on the nfs server is very subtly broken.

Close examination of the problematic server with uname -KU shows
1500053 1500051

On another machine, I configured sharenfs exactly the same way.
This one works.
uname -KU here is 1500053 1500053

Both machines are at 15.0-CURRENT #0 n278914-e0838f8a2e61. I didn't
notice the -KU before. 

I'm going to rebuild world, will post here with results.
--