From nobody Sat Oct 07 19:08:14 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 4S2vvv5csnz4xJY4 for ; Sat, 7 Oct 2023 19:08:27 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-oo1-xc31.google.com (mail-oo1-xc31.google.com [IPv6:2607:f8b0:4864:20::c31]) (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 4S2vvt47tHz4GY3 for ; Sat, 7 Oct 2023 19:08:26 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=U0sch3Ri; spf=pass (mx1.freebsd.org: domain of rick.macklem@gmail.com designates 2607:f8b0:4864:20::c31 as permitted sender) smtp.mailfrom=rick.macklem@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-oo1-xc31.google.com with SMTP id 006d021491bc7-57bb6b1f764so2014802eaf.2 for ; Sat, 07 Oct 2023 12:08:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696705704; x=1697310504; 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=lT3O6QD5jAvZfxRP46Es5CUETlaa6QaoS//QnQIUjYs=; b=U0sch3RiHC6Iy/3jjXQI3XIrADB3t4V1HUTCTTA0FKMphXsnW5y+X6GziN0hUO1q+T TRdyuYwvb9R8ogyjDNqFjQ0LdYGrMtHLeDjkCxKs7Wne3j3PYStyHkD3ahn0SbQFsieI LwHXm4Tp45r+BN+QuNzhfqRCabagaXnAhcCjXWlmTc8bvL4Z8+eQmFEwjKrIuv6Zc5E4 9kTIxwlKT2dSxgQd0tVfR8uhGSpZ3xWOLrDCYljVggtPC35OvQ7rYVgepu9yhYJ8iEKQ g5CUyDkcvjcGdAA5Ov07QmGQCYtegYJixGfzqvx5ajBuz4SMK3Po4T6pYkg4Q1kwuJAC 1gHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696705704; x=1697310504; 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=lT3O6QD5jAvZfxRP46Es5CUETlaa6QaoS//QnQIUjYs=; b=BZZb4TBPeMcMHRYZhuTDCEn7C+CAf/EGww2hnTh9EEizhSwotQoim4H5NJNgblmzWS qNrff822mWNizsWaashwJ1Bxj1YGSRrh/Pw4qiVlq7a+kzh6Q1nT1RRVoo3EpDPSOsCo g0Ghja07iDpf/OLuderR5X1RWgIXjYhczmR0LRC41EkCaka8c36M+BRXhYrUcfDfcljP iUvIeMDc0DwZKGd9mw9Kp28o+kr0EhP4+2m43hbdSO8s1XpzUGs7qF2vYfgSR1pl0YqV X6LJ9cHR2KvqZsIDzID/YAgvrMWrz4wWOXIMu/mqX8pF1KOQmWebYAN4vtOuwdiDvXD5 3fAw== X-Gm-Message-State: AOJu0YztZDmZXpCYR0+IkOZmY2d0gveSvTj/8CVm6n/AfpJhcaxc7PEQ LYLPW6UzLZ8eL0qS3Wc4ebaI/4XU3FAz6/qYnw== X-Google-Smtp-Source: AGHT+IE8MkD9VZ3pas4Qxwge46GZmRm6i9KFOQr5JvCazuE4lsx8o5wuNlHbwEprlDBTQrqWJNDVogUxeOxjKUlin7U= X-Received: by 2002:a05:6358:7299:b0:163:ce28:91ee with SMTP id w25-20020a056358729900b00163ce2891eemr5368399rwf.19.1696705704582; Sat, 07 Oct 2023 12:08:24 -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: Rick Macklem Date: Sat, 7 Oct 2023 12:08:14 -0700 Message-ID: Subject: Re: FreeBSD 13.2 NFS client mount hangs To: J David Cc: FreeBSD FS Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.87 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.87)[-0.874]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; 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::c31: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: 4S2vvt47tHz4GY3 On Sat, Oct 7, 2023 at 10:30=E2=80=AFAM J David w= rote: > > Here is a small pcap file obtained during a hang. This hang "feels" > different from the others. It was a different type of server and the > processes affected were different. But the symptoms are the same. (As > are the mount flags, etc., except this fs is mounted read-only.) > > It's not much; only 37 packets matched over about five minutes. I'll > try to get one I'm more confident is of the type previously discussed. > > Nonetheless I figured I'd pass this along in case it is helpful and/or > to confirm that this is the format you're looking for. Doesn't tell us much. If you look at it in wireshark (I just download and install it on a windows laptop), you'll see that the very first packet is the NFS server closing down the TCP connection (a FIN,ACK on a connection from port 800). Then the client establishes a new TCP connection and does Renew operations (just a Sequence operation by itself). Since there is no other RPCs than the Renews, I cannot guess why the server closed the connection, nor what the client is up to. The Sequence reply does note that the callback path is down, which is expected, given you are not running the nfscbd(8) daemon. One thing you could try is running the nfscbd(8) daemon. I suggested against doing so to avoid delegations, but it might be that this server does not handle that case well. To do so, add: nfscbd_enable=3D"YES" to the NFS client's /etc/rc.conf. --> It needs to be running before the mount is done, so the NFS client either needs to be rebooted or the NFS mount dismounted, the nfscbd started and then the NFS mount done again. Maybe this server will be happier with the callback path working? rick > > Thanks!