Date: Thu, 7 Nov 2024 13:59:36 -0800 From: Rick Macklem <rick.macklem@gmail.com> To: George Neville-Neil <gnn@neville-neil.com> Cc: Mark Saad <nonesuch@longcount.org>, freebsd-net@freebsd.org Subject: Re: An interesting anomaly in NFS client... Message-ID: <CAM5tNy7W9kHOFLoJWsU_1fU=%2BZ5OoDU7axw3izUv4GPWXpAF2A@mail.gmail.com> In-Reply-To: <9BD96F0F-363F-45BF-B3AF-BDEBD4B46175@neville-neil.com> References: <8187509e-c9fb-403f-8569-28ba58425cff@FreeBSD.org> <D1D03377-1A7B-47FA-B40D-2A30D0855F07@longcount.org> <9BD96F0F-363F-45BF-B3AF-BDEBD4B46175@neville-neil.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 7, 2024 at 9:34=E2=80=AFAM George Neville-Neil <gnn@neville-nei= l.com> wrote: > > > > On 7 Nov 2024, at 4:15, Mark Saad wrote: > > >> > >> On Nov 7, 2024, at 12:29=E2=80=AFAM, Andriy Gapon <avg@freebsd.org> wr= ote: > >> > >> =EF=BB=BFOn 07/11/2024 02:43, George Neville-Neil wrote: > >>> Howdy, > >>> We've been digging into an interesting possible issue in the FreeBSD = NFS client. Here is the scenario. I have a FreeBSD VM on my Mac, the Mac is= the NFS server, the VM is the client. > > > > What are you using to run the vm ? What architecture is the vm ? What a= bout 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 t= o 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. rick > > Best, > George >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM5tNy7W9kHOFLoJWsU_1fU=%2BZ5OoDU7axw3izUv4GPWXpAF2A>