Date: Thu, 24 Aug 2023 00:14:19 -0400 From: J David <j.david.lists@gmail.com> To: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: NFS client hang on 13.2-RELEASE-p2 on file locking / wrong interface selected Message-ID: <CABXB=RSvL_mpki7CW3V%2BtvqizVXX_Anbxwa4pg7uqT-wJvTw3Q@mail.gmail.com> In-Reply-To: <CABXB=RTGZ-4MDB7MBoDMzGU6K3xnVU8e7gxkzpGkA2sQ-Sw0Xw@mail.gmail.com> References: <CABXB=RTGZ-4MDB7MBoDMzGU6K3xnVU8e7gxkzpGkA2sQ-Sw0Xw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABXB=RSvL_mpki7CW3V%2BtvqizVXX_Anbxwa4pg7uqT-wJvTw3Q>