Major issues with nfsv4

[Rick Macklem]

Alan Somers wrote:
[stuff snipped]
>That's some good information.  However, it must not be the whole story.  I've >been nullfs mounting my NFS mounts for years.  For example, right now on a >FreeBSD 12.2-RC2 machine:
If I recall, you were one of the two people that needed to switch to
"minorversion=1" to get rid of NFSERR_BADSEQID (10026) errors.
Is that correct?

>> sudo nfsstat -m
>Password:
>192.168.0.2:/home on /usr/home
>nfsv4,minorversion=1,tcp,resvport,soft,cto,sec=sys,acdirmin=3,acdirmax=60,acreg>min=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=6553>6,readdirsize=65536,readahead=1,wcommitsize=16777216,timeout=120,retrans=>2147483647
Btw, using "soft" with NFSv4 mounts is a bad idea. (See the BUGS section of
"man mount_nfs".)

If you have a hung NFSv4 mount, you can use
# umount -N /usr/home
to dismount it. (It may take a couple of minutes.)

rick

> mount | grep home
192.168.0.2:/home on /usr/home (nfs, nfsv4acls)
/usr/home on /iocage/jails/rustup2/root/usr/home (nullfs)

Are you using any mount options with nullfs?  It might be worth trying to make the read-only mount into read-write, to see if that helps.  And what does "jls -n" show?
-Alan