From nobody Wed Jun 02 22:07:22 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 C660811D1215 for ; Wed, 2 Jun 2021 22:07:35 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f169.google.com (mail-oi1-f169.google.com [209.85.167.169]) (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 4FwNS749phz4sYV for ; Wed, 2 Jun 2021 22:07:35 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f169.google.com with SMTP id z3so4222002oib.5 for ; Wed, 02 Jun 2021 15:07:35 -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:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1m8gaPOmCWexqIyZQm6K3E392Dn7jAgIaLJ+VeVbmAQ=; b=GIsX3LtY+GZEYQXODsjZ/ilOWmU9MGprbVn9H3qgnjCy64Qm/AQ78UIzqR06zvYoUJ uc6VrmysAKugxdWRVOguFolcIa5lPkWVaFAbPjBBw9IH6Vr34y65OVlS8DUqJRQr4pAj RzkArMuJV8fpZmDqPUTE1yNcfrU4xYuxDHh07gSv1Lug4XESijykCQIozhDAbTzxELuu 8JWAX85534y9Tb2z50IwC4yKBA6OsX/Z8j7lh5ShpJCcTd5YOuAcElWeUGHfVRn+o7kb v0jgdeO/Mo3QIE5qlj4ngHTOg07L3QS+B3V9oTnKmhIKXZ31rtBJX1ovGpeVEzSztu8n 0pqw== X-Gm-Message-State: AOAM532QxYvFh3S8cA5eM4kNjr2e+5zGvRPMyg1BtZmpixUdevtItpu+ ND9YD6f7KderZefZbTYmyAxUDBgN2u0ZuHH9zzo= X-Google-Smtp-Source: ABdhPJyaWkjf5j3tZAxgu8P7Jry3hyZqAbCtk2ZTwN3AQwqiKjHmJ0tl1zC/IHuSNqVNGxXqycUZJNWspQdh8kRFChk= X-Received: by 2002:aca:e142:: with SMTP id y63mr23055869oig.57.1622671654271; Wed, 02 Jun 2021 15:07:34 -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 References: In-Reply-To: From: Alan Somers Date: Wed, 2 Jun 2021 16:07:22 -0600 Message-ID: Subject: Re: "nfs server not responding, timed out" with Linux client and 13.0-RELEASE server To: Rick Macklem Cc: freebsd-fs Content-Type: multipart/alternative; boundary="0000000000008a3e2005c3cfaf47" X-Rspamd-Queue-Id: 4FwNS749phz4sYV X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --0000000000008a3e2005c3cfaf47 Content-Type: text/plain; charset="UTF-8" On Tue, Jun 1, 2021 at 7:09 PM Rick Macklem wrote: > 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 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 > > -Alan > Thanks for the tip, Rick! I reverted the change mentioned in that PR, and everything seems fine so far. -Alan --0000000000008a3e2005c3cfaf47--