From nobody Tue Jun 01 21:20:05 2021 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 88983E7E66D for ; Tue, 1 Jun 2021 21:20:19 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f173.google.com (mail-oi1-f173.google.com [209.85.167.173]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FvlS16JFqz4pDT for ; Tue, 1 Jun 2021 21:20:17 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f173.google.com with SMTP id s19so724938oic.7 for ; Tue, 01 Jun 2021 14:20:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=2pjVotn7nmEdhKpyB0nkLaJs4yi5bhni2yid+LYyegU=; b=LOvDFbWqqEuHC5dfg0wqBkCQN2T61AsNLadeygordOtWwtL69UWeblzvQa0zMGtTkk I92eMn1iMPmS07ki4ovfWB1nt5hWeReUNju8zRQ8EAD1IhiTApFRpU4bt5AoBJt/9edW Ryp+s++cUu6nQY1nmZjwL+frcijZc5CWraFJ2LeSMdFDdh0f7ROFCl8oN1N2bjYuXAf5 yQstiaN0ej0sH3FVyLdnKONLSCeVY6oBcV4NFwRiJmHyWosrar2fP3H0eOlk84vi7Uu/ K54AgFTSfT67kUeJG10O2QI6+Tq4K1JGPZH/gBI9eDDEQSGKknBS5xSl9IvApl2jDolB iebg== X-Gm-Message-State: AOAM531wZ/ms1YDEWQU7gL0P4XxIPd/7AtB82MGv6sQF3TjcaSwdW8xE jl5nVbw4PxowC6ok24wXdVH/jPnKWQ+zKvEZXRWmEMsvXbY6HQ== X-Google-Smtp-Source: ABdhPJzDrtOuME9WSwNZiWLbzGAep+EbyndvKS7o6ZqGcGfRrT+Q6VQ9x5/Qt+34tvRM1kg3BNdv95lOTL3Jq+DZIaQ= X-Received: by 2002:aca:e142:: with SMTP id y63mr19232371oig.57.1622582415918; Tue, 01 Jun 2021 14:20:15 -0700 (PDT) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 From: Alan Somers Date: Tue, 1 Jun 2021 15:20:05 -0600 Message-ID: Subject: "nfs server not responding, timed out" with Linux client and 13.0-RELEASE server To: freebsd-fs Content-Type: multipart/alternative; boundary="000000000000850a8a05c3bae8a9" X-Rspamd-Queue-Id: 4FvlS16JFqz4pDT X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.167.173 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[209.85.167.173:from]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_DOM_EQ_FROM_DOM(0.00)[]; R_DKIM_NA(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[asomers]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[209.85.167.173:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[209.85.167.173:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.167.173:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-fs] X-ThisMailContainsUnwantedMimeParts: Y --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 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--