Date: Wed, 2 Jun 2021 01:09:17 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: Alan Somers <asomers@freebsd.org>, freebsd-fs <freebsd-fs@freebsd.org> Subject: Re: "nfs server not responding, timed out" with Linux client and 13.0-RELEASE server Message-ID: <YQXPR0101MB0968D693F45A87E0ACA991A7DD3D9@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <CAOtMX2iDcJYuAkFURigZNNZNHDWShK01%2BmmTpGWGHkd%2BSrwwqA@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
Alan Somers wrote: >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? See PR#256280 for the ways to fix this, rick -Alanhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQXPR0101MB0968D693F45A87E0ACA991A7DD3D9>