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 (clearly incorrect code) could actually cause the symptom [1]. 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 have to be re-done on the early state of the code in 2.3. Given the time involved, its quite likely the back port may not be done in time for trixie---it may have to wait until the first point release. But, it's important to understand that this bug has been around for years now, and upgrading to trixie from bookworm is not going to make the situation worse for anyone. I would recommend reducing the severity of this bug to important so that zfs is not removed from trixie. Best, Antonio Russo [1] https://github.com/openzfs/zfs/pull/17340#pullrequestreview-2847190346
