From nobody Fri Nov 8 14:29: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 4XlLtR1Xdsz5cKGg for ; Fri, 08 Nov 2024 14:29:35 +0000 (UTC) (envelope-from girgen@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XlLtR12kwz4cfW; Fri, 8 Nov 2024 14:29:35 +0000 (UTC) (envelope-from girgen@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1731076175; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=rSnhNhyUDViyB/vzHhW4ZtjDLXGOARwBclTTB1Co+9w=; b=xDXlolgo9RaeAe2KijKWwB9PSpI6klA4H4ygLNZmU9rXjSkOJBa2oh3TqrnHJX5c5v3wk6 mZZjvxJHtjl9a3K4uMzhTtMvHMADHdCrn3n6Ukqaj3uhHuUl2w4MYGBX9eHPtG3iTajluM Jk3LtIcJX1vDE4rxqN605VbPn+BzBxfvCjrk5kkOhqDEsFUcnefV0riR5MpdpE9a1my+y8 UoySnhnr/s8/jXri15zDkuxP2op93o57cvoJkS5+QWyl/iG7Lou0CMbYysC8SOhcmP5/5J BalEOAMcN7PiEw5FBaaYQtuV88nYtw3JAPTwSa81q1EMylxpQ9slUH0mvrAz9A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1731076175; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=rSnhNhyUDViyB/vzHhW4ZtjDLXGOARwBclTTB1Co+9w=; b=UnhsUR4UOUb2xeknf8h0Fh2oDZ1GcdvB6YXVlM82J/KZ+KERbrueTbAZaOg0lJlokpqaCO O+pnFRZ6VQylCoTjeoR6wt0I0fg/LqZXacNmbomL4yDnk4IVN4qktSgSKW01eKVpvWhmfV ALzP4ijxVs8QBL/NXE7dHrjLxehPm2bZ8CUqhNe+1FBTQ/rS9BZrFCxly15DDsXPOSS5YA mJmxK8mH229MyTRx8dzBEpj/dK4AUhVRrQ4ABnv+OYrJuIp2XwUiy+UeedmX0KdAXd31Ws i435dRkK70eCNqmcHlWEocAEv1at5j3Cu3TE5P4W0EQM/koPnQQ3oyGAn/J1ug== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1731076175; a=rsa-sha256; cv=none; b=yJtkyKWEcckO6TU04Lh/FP74FYjIyIwrNW8HVqGOGzaehBlmn3PnorbJhQsDkzVw+U6L2k 8miNrYtYRqPQ9FD7KdQ5QUiiRa8jVS7OqQQjtKrb/2n1KqmVQrOfidGI/PBIC7036GRKlD lAdc+kKUztFkXcv5ki9XB5xFE/iHYdm9p+DJx0lxjbMVKkXekdzQPwvX3ahDWozPoLRD61 DpzC98ajbJdXadmHZGA2C93dducp7Kop6VX6PFNajaSFhAxgYIKEpwLdqUoHhmgMx5RQ8+ 255gKfDnHc8Ip4ALGUDIBIMv8apYmu996sScZm3HoW98rFTzQFfFO7PvtEGvew== Received: from smtpclient.apple (visitor.bahnhof.se [213.136.33.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: girgen/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XlLtQ5QQ6zfCB; Fri, 8 Nov 2024 14:29:34 +0000 (UTC) (envelope-from girgen@FreeBSD.org) From: Palle Girgensohn Message-Id: <3E85AAAE-8B1E-47C7-B581-E3D98AB03907@FreeBSD.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_6FFFCB03-1F59-4ADF-8B24-40751C8D519A" 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 (Mac OS X Mail 16.0 \(3826.200.121\)) Subject: Re: zfs snapshot corruption when using encryption Date: Fri, 8 Nov 2024 15:29:22 +0100 In-Reply-To: Cc: freebsd-fs@freebsd.org To: void References: <03E4CCF5-0F9A-4B0E-A9DA-81C7C677860C@FreeBSD.org> X-Mailer: Apple Mail (2.3826.200.121) --Apple-Mail=_6FFFCB03-1F59-4ADF-8B24-40751C8D519A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > 8 nov. 2024 kl. 14:50 skrev void : >=20 > On Fri, Nov 08, 2024 at 10:57:43AM +0100, Palle Girgensohn wrote: >> Hi! >>=20 >> We se sporadical corruption in snapshots (not really files, it seems) = since we started using encryption on previously well behaved system. >>=20 >> 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. >>=20 >> I filed a bug report: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282622 >>=20 >> Any ideas? >=20 > 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? I cannot run `zfs send -I fs@previous_snap fs@problematic_snap`, I get warning: cannot send 's@problematic_snap': Input/output error` Removing the snapshot fixes the problem.= --Apple-Mail=_6FFFCB03-1F59-4ADF-8B24-40751C8D519A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

8 nov. 2024 kl. 14:50 skrev void <void@f-m.fm>:

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=3D282622

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?

I cannot run `zfs send -I fs@previous_snap = fs@problematic_snap`, I get

warning: cannot send 's@problematic_snap': Input/output = error`

Removing the snapshot fixes the = problem.= --Apple-Mail=_6FFFCB03-1F59-4ADF-8B24-40751C8D519A--