From nobody Fri Nov 8 13:50:22 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 4XlL1H27mGz5cljC for ; Fri, 08 Nov 2024 13:50:27 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fhigh-b5-smtp.messagingengine.com (fhigh-b5-smtp.messagingengine.com [202.12.124.156]) (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 4XlL1F6250z4WWl for ; Fri, 8 Nov 2024 13:50:25 +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=I1CRz60H; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=CPXcvBLI; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 202.12.124.156 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from phl-compute-10.internal (phl-compute-10.phl.internal [10.202.2.50]) by mailfhigh.stl.internal (Postfix) with ESMTP id 80246254012A for ; Fri, 8 Nov 2024 08:50:24 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-10.internal (MEProxy); Fri, 08 Nov 2024 08:50:24 -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=1731073824; x=1731160224; bh=6OBn+qHSak LhcPUkTsgyqMSdTaB/orynDbmCjKP8m8w=; b=I1CRz60HsyFljyRenETsp52YnI wBMWstDYXAxw10US0IsxJrV9JwroCbibmE2HTNAJ7W/K6dV4xLqAq2Jyajy0ulOu wmwpI55RBAhIneZF2ZP7eaCrjbI5RYweeYT2LE26Xd9Lw8vXP7mndRpymZPyEv1b rXe9bYa2ugJDlQPHcHztKoIYMZvTKtMZkWVf+39QTG94szg5kxizM29pkL+1vnqP lbG0tjQVhQxbpKdU75fUathBHU485WAPgX8EmMtvQdJZ/9yA6wblVVmbdHu9Zdkn DJ4MLcLxmwd2TZ7MsCNbhhOo7GzNs/d+e2Tr+HLMHoxuSYbYBr5rx0+XzsLA== 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= 1731073824; x=1731160224; bh=6OBn+qHSakLhcPUkTsgyqMSdTaB/orynDbm CjKP8m8w=; b=CPXcvBLIOjHRda6FP6T3y1i6x3UAuJjMx9y+gfNmBe+GU7VSbzD 3Quxwwjt/oo50kujMLlzA41mt1Nxk0SLzCJ6MlkVx4hd6zDU84+GW4JdjAlE2xbK DmWzsy/QZRmucFYa85bDLP2gima+3QnBtNVPX6jmDo7Wt6KaYJpEbUtXqMd1Tc+Z JcsLciIYZ6w1jw8l9kznvuYthJpIt12yvWCe3IMw5FlsKwSb7qWK877ICncJfyPl TN18/D9Y1fAwUXO9Y4RXCVktJmAOa9lCxUIR3y4dUonGA1PDolO0y6ovPc20wtcL SWdJ4s/wdJAtK0C2jQ1BQ7yY7B/ZQ09YppQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrtdeigdehfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukf hfgggtuggjsehttdertddttddvnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdr fhhmqeenucggtffrrghtthgvrhhnpeeivdevueehffdtfffhvdefhefghfeikeetudffvd eitdfftdekudeileegffetheenucffohhmrghinhepghhithhhuhgsrdgtohhmpdhfrhgv vggsshgurdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepvhhoihgusehfqdhmrdhfmhdpnhgspghrtghpthhtohepuddpmhhouggvpehs mhhtphhouhhtpdhrtghpthhtohepfhhrvggvsghsugdqfhhssehfrhgvvggsshgurdhorh hg X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Fri, 8 Nov 2024 08:50:23 -0500 (EST) Date: Fri, 8 Nov 2024 13:50:22 +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> 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: <03E4CCF5-0F9A-4B0E-A9DA-81C7C677860C@FreeBSD.org> 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)[-1.000]; 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:202.12.124.128/27]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[202.12.124.156:from]; FREEMAIL_FROM(0.00)[f-m.fm]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; 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]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[202.12.124.156:from]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Rspamd-Queue-Id: 4XlL1F6250z4WWl X-Spamd-Bar: --- On Fri, Nov 08, 2024 at 10:57:43AM +0100, Palle Girgensohn wrote: >Hi! > >We se sporadical corruption in snapshots (not really files, it seems) since we started using encryption on previously well behaved system. > >There a description in the OpenZFS github, https://github.com/openzfs/zfs/issues/12014 , that seems to be spot on. The issue is still open. > >I filed a bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282622 > >Any ideas? No idea but i'd like to ask, in your context: do the snapshots get created, and if so, can you restore from them? In other words, does the 'corruption' fix itself, with zfs self-healing? --