Date: Tue, 1 Jun 2021 15:20:05 -0600 From: Alan Somers <asomers@freebsd.org> To: freebsd-fs <freebsd-fs@freebsd.org> Subject: "nfs server not responding, timed out" with Linux client and 13.0-RELEASE server Message-ID: <CAOtMX2iDcJYuAkFURigZNNZNHDWShK01%2BmmTpGWGHkd%2BSrwwqA@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
--000000000000850a8a05c3bae8a9 Content-Type: text/plain; charset="UTF-8" I have several Linux NFS clients (Debian, with various 4.9 kernels) mounting NFS 4.0 from both Solaris and FreeBSD (mostly 12.2-RELEASE) servers. I frequently see kernel messages in the clients about "nfs: server <HOSTNAME> not responding, timed out" for both the FreeBSD and Solaris servers. It usually recovers after a few seconds. However, on the sole 13.0-RELEASE server, the hangs last for minutes to hours. tcpdump/wireshark shows the NFS client sending a "V4 Call SEQUENCE" packet every 5-10 seconds, all with the same sessionid. The server responds with a TCP ACK, but sends no NFS-level response. I've seen this with both NFS 4.0 and 4.2. NFS delegations are disabled, and nfsdumpstate shows that the client has callbacks enabled, with 2-4 opens, openowners, locks, and lockowners. Can anybody suggest how to fix or further debug this problem? -Alan --000000000000850a8a05c3bae8a9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2iDcJYuAkFURigZNNZNHDWShK01%2BmmTpGWGHkd%2BSrwwqA>