On Tue, 20 May 2025 05:54:30 -0600 Antonio Russo wrote:
See also [1], which presumably will cherry-pick the fix onto 2.2
without changes. If that is indeed the case, we should probably
cherry pick it as is, too.
One of the other patches referenced in that discussion ([1]) should
probably be i
See also [1], which presumably will cherry-pick the fix onto 2.2
without changes. If that is indeed the case, we should probably
cherry pick it as is, too.
Best,
Antonio Russo
[1] https://github.com/openzfs/zfs/pull/17325
On 2025-05-19 11:24, Florian Bach wrote:
Am 19.05.25 um 07:46 schrieb Antonio Russo:
There is progress on this, but it is occurring in real time. My suggestion
is to wait for upstream to decide they understand it, finalize the PR, merge
it, and then back port the fix to 2.3. This last step m
Am 19.05.25 um 07:46 schrieb Antonio Russo:
There is progress on this, but it is occurring in real time. My suggestion
is to wait for upstream to decide they understand it, finalize the PR,
merge
it, and then back port the fix to 2.3. This last step may be painful,
since
the analysis may
Control: found -1 2.0.3-1
I too have been watching this. This patch has both resolved the reproducer
and some other real-world cases (in fact, I'm unaware of anyone experiencing
the corruption after using the patch).
However, in the (draft) pull request, there is discussion over how the
(clearl
Package: zfs-dkms
Version: 2.3.2-1
Severity: grave
Tags: upstream patch
Dear Maintainer,
since the release of ZFS 2.0.0 back in 2020, ZFS contains a corruption
bug where snapshots and/or a dataset can get corrupted when using ZFS
encryption, if you're performing a "zfs send" at the same time a
6 matches
Mail list logo
