Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Nov 2024 15:29:22 +0100
From:      Palle Girgensohn <girgen@FreeBSD.org>
To:        void <void@f-m.fm>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: zfs snapshot corruption when using encryption
Message-ID:  <3E85AAAE-8B1E-47C7-B581-E3D98AB03907@FreeBSD.org>
In-Reply-To: <Zy4XHlKodLu7utBa@int21h>
References:  <03E4CCF5-0F9A-4B0E-A9DA-81C7C677860C@FreeBSD.org> <Zy4XHlKodLu7utBa@int21h>

next in thread | previous in thread | raw e-mail | index | archive | help

--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 <void@f-m.fm>:
>=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

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"><br =
style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 13px; font-style: normal; font-variant-caps: =
normal; font-weight: 400; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><br style=3D"caret-color: rgb(0, 0, 0); color: =
rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 13px; font-style: =
normal; font-variant-caps: normal; font-weight: 400; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><blockquote =
type=3D"cite" style=3D"font-family: Menlo-Regular; font-size: 13px; =
font-style: normal; font-variant-caps: normal; font-weight: 400; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;">8 nov. 2024 kl. 14:50 skrev void &lt;void@f-m.fm&gt;:<br><br>On =
Fri, Nov 08, 2024 at 10:57:43AM +0100, Palle Girgensohn =
wrote:<br><blockquote type=3D"cite">Hi!<br><br>We se sporadical =
corruption in snapshots (not really files, it seems) since we started =
using encryption on previously well behaved system.<br><br>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.<br><br>I filed a bug report: =
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282622<br><br>Any =
ideas?<br></blockquote><br>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?<br></blockquote><br style=3D"caret-color: rgb(0, 0, 0); =
color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 13px; =
font-style: normal; font-variant-caps: normal; font-weight: 400; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><span style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); =
font-family: Menlo-Regular; font-size: 13px; font-style: normal; =
font-variant-caps: normal; font-weight: 400; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; display: inline =
!important; float: none;">I cannot run `zfs send -I fs@previous_snap =
fs@problematic_snap`, I get</span><br style=3D"caret-color: rgb(0, 0, =
0); color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 13px; =
font-style: normal; font-variant-caps: normal; font-weight: 400; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><br style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); =
font-family: Menlo-Regular; font-size: 13px; font-style: normal; =
font-variant-caps: normal; font-weight: 400; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><span =
style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 13px; font-style: normal; font-variant-caps: =
normal; font-weight: 400; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; display: inline !important; float: =
none;">warning: cannot send 's@problematic_snap': Input/output =
error`</span><br style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); font-family: Menlo-Regular; font-size: 13px; font-style: normal; =
font-variant-caps: normal; font-weight: 400; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><br =
style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 13px; font-style: normal; font-variant-caps: =
normal; font-weight: 400; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><span style=3D"caret-color: rgb(0, 0, 0); color: =
rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 13px; font-style: =
normal; font-variant-caps: normal; font-weight: 400; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; text-decoration: none; display: =
inline !important; float: none;">Removing the snapshot fixes the =
problem.</span></body></html>=

--Apple-Mail=_6FFFCB03-1F59-4ADF-8B24-40751C8D519A--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E85AAAE-8B1E-47C7-B581-E3D98AB03907>