Date: Fri, 17 Nov 2023 18:19:05 -0600 From: Mike Karels <mike@karels.net> To: Garrett Wollman <wollman@bimajority.org> Cc: freebsd-stable@freebsd.org Subject: Re: NFS exports of ZFS snapshots broken Message-ID: <36C8AB52-B78A-4515-8849-3CC46C5AF1A6@karels.net> In-Reply-To: <5D602618-7031-4D0E-A439-6A3E4F174926@karels.net> References: <25943.54632.572766.121032@hergotha.csail.mit.edu> <E5F6DD43-6CF9-44E3-A008-2EBEA287BA40@karels.net> <25943.60056.880614.452966@hergotha.csail.mit.edu> <5D602618-7031-4D0E-A439-6A3E4F174926@karels.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17 Nov 2023, at 17:22, Mike Karels wrote: > On 17 Nov 2023, at 16:35, Garrett Wollman wrote: > >> <<On Fri, 17 Nov 2023 15:57:42 -0600, Mike Karels <mike@karels.net> said: >> >>> I have not run into this, so I tried it just now. I had no problem. >>> The server is 13.2, fully patched, the client is up-to-date -current, >>> and the mount is v4. >> >> On my 13.2 client and 13-stable server, I see: > > I set up ZFS on a 13-stable system that doesn't normally run ZFS. > Mounting from a 13.2 system using v3, I get the EIO errors. Unless there > is some other variable, it sounds like something broke in the nfs server > code between 13.2 and a month or so ago (my 13-stable kernel is from > Oct 7). Looks like main still has this problem. I exported a ZFS file system from a 15-current system to the same 13.2 client, and it exhibits the problem (EIO from NFSv3). So the problem is most likely in 14.0 as well. Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36C8AB52-B78A-4515-8849-3CC46C5AF1A6>