Is there any update about this bug report yet? Will the fix be
backported to the current release or will zfs 2.3.3 still make it into
trixie?
ZFS 2.3.3 which includes all these fixes has been released last
Thursday. Is there any work being done either getting this version
packaged, or back-po
On 2025-05-29 06:11, Aron Xu wrote:
I'm doing a cherry-pick from 2.3.3-staging at the moment, for a set of
patches that should be acceptable by the release team, if 2.3.3 isn't
to be released very soon. We can still try to request for an exception
after 2.3.3 actually comes out.
For what it's w
On Thu, May 29, 2025 at 11:57 AM Florian Bach wrote:
>
> Quick update, the changes we're talking about (pull requests 17340 and
> 17353) have now been merged into the 2.3.3-staging branch so it looks
> like they'll definitely be part of the next 2.3.3 release.
>
> Would it be better to backport th
Quick update, the changes we're talking about (pull requests 17340 and
17353) have now been merged into the 2.3.3-staging branch so it looks
like they'll definitely be part of the next 2.3.3 release.
Would it be better to backport these two commits into Debian's 2.3.2
(the two commits seem to
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
10 matches
Mail list logo
