From nobody Fri Nov 8 05:41:30 2024 X-Original-To: freebsd-net@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 4Xl79F6HB6z5c8y4 for ; Fri, 08 Nov 2024 05:41:37 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xl79F1C8Bz4y06 for ; Fri, 8 Nov 2024 05:41:37 +0000 (UTC) (envelope-from gnn@neville-neil.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of gnn@neville-neil.com designates 217.70.183.197 as permitted sender) smtp.mailfrom=gnn@neville-neil.com; dmarc=none Received: by mail.gandi.net (Postfix) with ESMTPSA id 6F9101C0006; Fri, 8 Nov 2024 05:41:33 +0000 (UTC) From: George Neville-Neil To: Rick Macklem Cc: Mark Saad , freebsd-net@freebsd.org Subject: Re: An interesting anomaly in NFS client... Date: Thu, 07 Nov 2024 21:41:30 -0800 X-Mailer: MailMate (1.14r5937) Message-ID: In-Reply-To: References: <8187509e-c9fb-403f-8569-28ba58425cff@FreeBSD.org> <9BD96F0F-363F-45BF-B3AF-BDEBD4B46175@neville-neil.com> List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-GND-Sasl: gnn@neville-neil.com X-Spamd-Result: default: False [-1.01 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_MEDIUM(0.54)[0.540]; R_SPF_ALLOW(-0.20)[+ip4:217.70.183.192/28]; RWL_MAILSPIKE_VERYGOOD(-0.20)[217.70.183.197:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[217.70.183.197:from]; NEURAL_SPAM_SHORT(0.05)[0.049]; ARC_NA(0.00)[]; ASN(0.00)[asn:29169, ipnet:217.70.176.0/20, country:FR]; FREEFALL_USER(0.00)[gnn]; MIME_TRACE(0.00)[0:+]; TO_DN_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[neville-neil.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TAGGED_RCPT(0.00)[]; MLMMJ_DEST(0.00)[freebsd-net@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4Xl79F1C8Bz4y06 X-Spamd-Bar: - On 7 Nov 2024, at 13:59, Rick Macklem wrote: > On Thu, Nov 7, 2024 at 9:34=E2=80=AFAM George Neville-Neil wrote: >> >> >> >> On 7 Nov 2024, at 4:15, Mark Saad wrote: >> >>>> >>>> On Nov 7, 2024, at 12:29=E2=80=AFAM, Andriy Gapon = wrote: >>>> >>>> =EF=BB=BFOn 07/11/2024 02:43, George Neville-Neil wrote: >>>>> Howdy, >>>>> We've been digging into an interesting possible issue in the FreeBS= D NFS client. Here is the scenario. I have a FreeBSD VM on my Mac, the Ma= c is the NFS server, the VM is the client. >>> >>> What are you using to run the vm ? What architecture is the vm ? What= about the Mac ? >> >> qemu, aarch64, M3 Mac. >> >> I doubt this is the source of the issue. >> >> I was poking through the code and I wonder if a slight time skew might= be an issue. I'm going to check into that. The VM and the Mac both us = NTP to stay in sync with the world, but who knows... > Hi George, > > I'll take a look at the packet trace later, but... > > If you can easily reproduce the issue, do a: > # nfsstat -E -c -z > - before reproducing it, and a > # nfsstat -E -c > - after. Then look at the Cache Info: at the end of the output. > I'll give that a look, and the thing that Mark found is also interesting.= I might ask Warner about it tomorrow, we're both at the Dev Summit. Thanks, George