From nobody Sat Nov 18 00:19:05 2023 X-Original-To: freebsd-stable@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 4SXDsd0x9vz51X7H for ; Sat, 18 Nov 2023 00:19:17 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail2.karels.net (mail2.karels.net [3.19.118.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "freebsd", Issuer "freebsd" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SXDsc0GL7z4WRg for ; Sat, 18 Nov 2023 00:19:15 +0000 (UTC) (envelope-from mike@karels.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=karels.net header.s=mail2 header.b=YNmfSVMn; spf=pass (mx1.freebsd.org: domain of mike@karels.net designates 3.19.118.201 as permitted sender) smtp.mailfrom=mike@karels.net; dmarc=none Received: from mail2.karels.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail2.karels.net (8.17.1/8.17.1) with ESMTP id 3AI0J5FT055300; Fri, 17 Nov 2023 18:19:05 -0600 (CST) (envelope-from mike@karels.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=karels.net; s=mail2; t=1700266745; bh=xAC/OdV4xj6M2RZGqYYvYgwODrHDVVznmW0N74SIRXQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=YNmfSVMnJxyPcJZ/zHFG/zkVocqSk5SzaZEULwWwO2QpM8uraU4UA03b9ctIz4Xs6 Lt29E+KMCoNPnFyGeKYsSl3BDTvVJ3vEDBvUelTaqDcqAEnY/TlJp0p/fEkW/hGWj/ avxdzINClavfPv2uUWJ9YBLZOBEP4uQA6FpS7I3q40wc9nqOVzhELjoNyCFfJDijg6 hj2N7Fi7CBcNelf53VniRFep0nKPRUbn2zmgwm+AYJUqbJPjrAtFU3U+NJ57kO93tq j5j44mcqz2YI1vZmwkJnkDxx66aSsenVsBAOk8sJ54wZHuP7LpJwkNljii5DPccwV+ ZANwVTvIheCGQ== Received: from [10.0.2.130] ([73.62.165.147]) by mail2.karels.net with ESMTPSA id JN+xLPkCWGUC2AAAs/W3XQ (envelope-from ); Fri, 17 Nov 2023 18:19:05 -0600 From: Mike Karels To: Garrett Wollman Cc: freebsd-stable@freebsd.org Subject: Re: NFS exports of ZFS snapshots broken Date: Fri, 17 Nov 2023 18:19:05 -0600 X-Mailer: MailMate (1.14r5964) 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> <25943.60056.880614.452966@hergotha.csail.mit.edu> <5D602618-7031-4D0E-A439-6A3E4F174926@karels.net> List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain X-Spamd-Result: default: False [-3.49 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.993]; R_SPF_ALLOW(-0.20)[+ip4:3.19.118.201]; R_DKIM_ALLOW(-0.20)[karels.net:s=mail2]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; ASN(0.00)[asn:16509, ipnet:3.16.0.0/14, country:US]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; DKIM_TRACE(0.00)[karels.net:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FREEFALL_USER(0.00)[mike]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[karels.net]; TO_DN_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4SXDsc0GL7z4WRg X-Spamd-Bar: --- On 17 Nov 2023, at 17:22, Mike Karels wrote: > On 17 Nov 2023, at 16:35, Garrett Wollman wrote: > >> < 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