From nobody Sat Nov 09 01:59:35 2024 X-Original-To: freebsd-fs@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 4XlfBg5rybz5d739 for ; Sat, 09 Nov 2024 01:59:39 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fout-a5-smtp.messagingengine.com (fout-a5-smtp.messagingengine.com [103.168.172.148]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XlfBf6BG0z4qyc for ; Sat, 9 Nov 2024 01:59:38 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b="U6T2w2U/"; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=hiMLXjp6; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.148 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from phl-compute-09.internal (phl-compute-09.phl.internal [10.202.2.49]) by mailfout.phl.internal (Postfix) with ESMTP id 85BD31380368 for ; Fri, 8 Nov 2024 20:59:37 -0500 (EST) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-09.internal (MEProxy); Fri, 08 Nov 2024 20:59:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1731117577; x=1731203977; bh=GYWr5PU40o ETdnsxpNlF1PDDq08AFcxlhzdy1VQnVz8=; b=U6T2w2U/rGp2GxWLGjODTL2bbd +iLT4jB+OXJwBn0R/87TPOY+Xz0gPvptPPPN5YqOGUGu4nTgAABhEZISTl1JjAF8 exA/z1EjtHejtL/Adn73Ohub39qS9xLJKalWLeB0JOdePsuFcN8Gutvx73kOgwMG HyALoV7U87n2hMRiKI7AeaDU4LzlsoI4qg6TyN4ukXAQEgAwdS7+Zl+tyMWSGf/7 zaip13BBiPbfMASPUaiBqXj2BOSh/zOV/K+AZu/LxrsJ3iwR5rCl7KVC9OnSX8bi ElEtU/VVM2WUUhfWxkKNkk/g2Mv+jk2AesIoOPpp5JlC7Z9ld1v/7kIJdaqA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1731117577; x=1731203977; bh=GYWr5PU40oETdnsxpNlF1PDDq08AFcxlhzd y1VQnVz8=; b=hiMLXjp6bF1I8cUbYAddFUHXfhSgGipTmDmls/+4++CWQhDAUt6 aCwGxtZivHkk2Ek7lpetMHJ8+MGah6MUxYcYL17OBDKxdlM5AhSjL7kKRdr/GwMF 4iVf9lENFBmMPFDmO79t6zLz2ccUH+tskz6qoi1G7TLBZLHw3IhZoJi0qf1FyItM fuhuXuK+xnDkD/oAP9FzRV3uQobfNG8SNLykrs9yDoyLw6psW+TxKDsugnoeZvTn 8+aCEaAdTMXvNk7UXVIAa9D2U97EifABSWHdMuQY3LbFofngg7R10LXF/ee+k4ts Cm/V2NEuaLALaIBmYcDqeihJbmHP89R9aIg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrtdejgdegudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukf hfgggtuggjsehttdertddttddvnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdr fhhmqeenucggtffrrghtthgvrhhnpedthfehueetjeduffekhfdthfefkeegtddvieetve fgjedtgfeffffhueeiledtieenucffohhmrghinhepfhhrvggvsghsugdrohhrghenucev lhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehvohhiugesfh dqmhdrfhhmpdhnsggprhgtphhtthhopedupdhmohguvgepshhmthhpohhuthdprhgtphht thhopehfrhgvvggsshguqdhfshesfhhrvggvsghsugdrohhrgh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Fri, 8 Nov 2024 20:59:36 -0500 (EST) Date: Sat, 9 Nov 2024 01:59:35 +0000 From: void To: freebsd-fs@freebsd.org Subject: Re: zfs snapshot corruption when using encryption Message-ID: Mail-Followup-To: freebsd-fs@freebsd.org References: <03E4CCF5-0F9A-4B0E-A9DA-81C7C677860C@FreeBSD.org> <3E85AAAE-8B1E-47C7-B581-E3D98AB03907@FreeBSD.org> List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-3.60 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.148:from]; FREEMAIL_FROM(0.00)[f-m.fm]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; MISSING_XM_UA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Rspamd-Queue-Id: 4XlfBf6BG0z4qyc X-Spamd-Bar: --- On Fri, Nov 08, 2024 at 11:11:23PM +0100, Palle Girgensohn wrote: >$ freebsd-version -ku >14.0-RELEASE-p10 >14.0-RELEASE-p10 > >dunno how to present in the above fashion? Binary install, not from source. % zfs version >The latter, zfs per-filesystem zfs encryption. I haven't heard any horror >stories about it, albeit it's quite fresh code. I'm wrong about native zfs encryption not being on 14.0. Seems like it is. https://www.freebsd.org/releases/14.0R/relnotes/ I'm reading this bit: ### ZFS Changes OpenZFS has been upgraded to version 2.2. New features include: block cloning, which allows shallow copies of blocks in file copies. This is optional, and disabled by default; it can be enabled with sysctl vfs.zfs.bclone_enabled=1. scrub error log (zpool scrub -e) BLAKE3 checksums, which are fast, and are now the recommended secure checksums corrective zfs receive can heal corrupted data vdev and zpool user properties, similar to dataset user properties. ### Then again, 14.0 is EoL. >Na, it's JBOD alright. I see nothing weird with the disks. >> Reallocated_Sector_Ct >> Reported_Uncorrect >> Current_Pending_Sector >> Offline_Uncorrectable Were all these values '0' ? Using truss might give a clue about the failure: # truss -o /tmp/truss.out zfs-send-commands make sure the outfile is made in a place with lots of spare space. --