From nobody Fri Oct 06 17:47:51 2023 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 4S2G9d0pdsz4vyyH for ; Fri, 6 Oct 2023 17:48:05 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4S2G9c2ywGz4bjv for ; Fri, 6 Oct 2023 17:48:04 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=ZyIV2ubq; spf=pass (mx1.freebsd.org: domain of jdavidlists@gmail.com designates 2607:f8b0:4864:20::52d as permitted sender) smtp.mailfrom=jdavidlists@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-pg1-x52d.google.com with SMTP id 41be03b00d2f7-5855333fbadso1634030a12.1 for ; Fri, 06 Oct 2023 10:48:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696614483; x=1697219283; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=F//jLIJFu1mvbKvAzXQBAb3cfMCz9X7yMb4BAA2dLC4=; b=ZyIV2ubq6dRuPMo7mZbXKNZnGlaAkOk/XjiHk1u2FYKb91VonYNrQiBsnNC0/WTFcY eiOuNSFwumkaMUdQrTp/1BOH2UCEq+O8PLOzREF9dtHrM4EBtF0eRwAotimBhgWCv6PL Njmn5Q8MWvznMmHiP/FxqzkVODKpIHnl6I0R3dUg9hMO4qDpGwW1sdoK7jBvimWZPRh5 xSLmaMkZdDYRkTBPMULvHOt9HxWza3JgdgcPKYtn5tU8BK5C7db5jOxr0OQIXi65CFjG x1hTt3tRJ9nOiiIogvDLjlxpilhHPTm7lC54cpKC2qXYdNDl3Y+9lD+TyfKhglmfiPbj iKZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696614483; x=1697219283; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=F//jLIJFu1mvbKvAzXQBAb3cfMCz9X7yMb4BAA2dLC4=; b=Rov2r/pWbbHAMiBhkycn+8N5KX3Thm5W4bTEMl/pM4EKUa6tL99zUl+cdoRBLks6r+ 66k1YmVUID/0XpS7DgwcanAKnloSfa4yQFjOQYXbON7mjgPHiwX9z/kpv4aOtCOgeQcj EjfEIBx9DjqpsHBhPd1nagb4GH2sur80+Tjc1SRYLresF5diVSPTsIcZ7t+0i2zwGsw5 2V5ax7qNBuFfzGJPlRWiA5AgCFumF159DJR2Bj30wIihTgrqGp0bHU+YR6WtltxoOuZM 9hzAHcVaWROFQnr6P8gA9O/jiMjzDoUPAycGFF2blSnI7G5ByRiZcv1yAw0XMNHc9BmR Hl1Q== X-Gm-Message-State: AOJu0Yw3HmTStOCp2MxWPF+/f7wpV0P+SGTv+GZrwoExHBZilcKzOQWN KatgBV65FT+w7LHjHY75XZg7jL+JpJ7+uJepe+Btz4O+WSo= X-Google-Smtp-Source: AGHT+IEErR9HO/R7/4ifSfeWKsJOHQKySzT4jdcqFwH2UnqNs7jYfWA+5UQ8GWxJ40buzQZ3RmZLqhMUWnjjDxdKdLU= X-Received: by 2002:a17:90b:1bc7:b0:26d:4ab3:fe11 with SMTP id oa7-20020a17090b1bc700b0026d4ab3fe11mr8185172pjb.24.1696614482782; Fri, 06 Oct 2023 10:48:02 -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: J David Date: Fri, 6 Oct 2023 13:47:51 -0400 Message-ID: Subject: Re: FreeBSD 13.2 NFS client mount hangs To: Rick Macklem Cc: FreeBSD FS Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.986]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TAGGED_RCPT(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::52d:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; TAGGED_FROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[] X-Rspamd-Queue-Id: 4S2G9c2ywGz4bjv On Mon, Oct 2, 2023 at 7:08=E2=80=AFPM Rick Macklem wrote: > > The nfscbd daemon is not running on any of the clients. > > > > > If the Linux server still > > > issues delegations > > > > How would I determine that? > nfsstat -E -c > and then look at the number under "Delegs". It is a current count of > delegations, so if it remains 0 over time, no delegations are being issue= d. But if this is done from a client that is not running nfscbd, isn't it pretty well guaranteed to be zero? Checking all the clients I can find, "Deleg" is zero on all of them. On about half, "DelegRet" is nonzero but small (1-100), but I don't know what that is or if it's related. > I have attached a small patch which should make the NFS client handle > this error correctly. I will look for a way to try this patch, but the clients in this case are all managed with freebsd-update and don't have enough disk space to build a kernel locally, so it may be tricky. > > > # tcpdump -s 0 -w out.pcap host > > > Let this run for a while and then pull out.pcap into wireshark and se= e what > > > traffic is going between the NFS client and server. > > > (Unlike tcpdump, wireshark does know how to decode NFS properly.) > > > > If/when the issue happens again, I will attempt to do this and report b= ack. I am also working on getting access to Wireshark. In the interim, it did happen again, so the best I can do is put a little bit of tcpdump output here: https://pastebin.com/UDrphwr5 . I can't vouch for "correct" but it does mostly seem to decode the NFS packe= ts. It seems to loop the same couple of actions with long delays (15 seconds) between retries: This sequence: +0.0000s: Client -> server xid 1205841201 getattr fh 0,7/2 ("Getattr" in packet body) +1.4106s: Client -> server xid 1205841202 getattr fh 0,5/2 ("Renew" in packet body) +0.0002s: Server -> client xid 1205841202 getattr LNK 12231267145 ids 1/53 sz 0 ("Renew" in packet body) +3.8001s: Server -> client xid 1205841201 getattr ERROR: Request couldn't be completed in time ("Getattr" in packet body) Repeats after 15 seconds: +15.0090s: client -> server 1205841203 getattr fh 0,7/2 ("Getattr" in packet body) ... etc The "fh 0,7/2" and "fh 0,5/2" seem to be consistent each time. The xid (transaction/request ID?) increments each time. Maybe that will provide a lucky flash of insight in the interim. Thanks!