Date: Thu, 07 Nov 2024 09:33:37 -0800 From: George Neville-Neil <gnn@neville-neil.com> To: Mark Saad <nonesuch@longcount.org> Cc: freebsd-net@freebsd.org Subject: Re: An interesting anomaly in NFS client... Message-ID: <9BD96F0F-363F-45BF-B3AF-BDEBD4B46175@neville-neil.com> In-Reply-To: <D1D03377-1A7B-47FA-B40D-2A30D0855F07@longcount.org> References: <8187509e-c9fb-403f-8569-28ba58425cff@FreeBSD.org> <D1D03377-1A7B-47FA-B40D-2A30D0855F07@longcount.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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= to stay in sync with the world, but who knows... Best, George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9BD96F0F-363F-45BF-B3AF-BDEBD4B46175>