Re: NFS client hang on 13.2-RELEASE-p2 on file locking / wrong interface selected

A little bit of a codicil to this, something interesting happened
while cleaning up from my tests. I briefly accidentally unexported all
filesystems on the server. The instant I did that, NFS-using processes
on the client side immediately went to nlmrvc, 100% CPU usage, and
started spamming the server with the same type of messages (using the
correct network this time).

As soon as I re-exported the filesystems, everything cleared up.

So it seems like there may be a secondary issue on the FreeBSD client
side. Perhaps it is getting some sort of "permission denied" error and
retrying way too fast. (During the test shown in my earlier message,
nothing was exported to 172.17.0.0, so the server might reject any
access from there in the same way as this.)

If so, perhaps the packet dumps from my original message will help identify it.

Thanks!