Re: Debian 12.5.0 amd64 and OpenZFS bug #15526
On Tue 27/02/2024 at 22:52, David Christensen <dpchrist@holgerdanske.com> wrote:
> ...
> These appear to be the ZFS packages for the available Debian releases:
>
> https://packages.debian.org/buster/zfs-dkms
>
> buster zfs-dkms (0.7.12-2+deb10u2)
> buster-backports zfs-dkms (2.0.3-9~bpo10+1)
> bullseye zfs-dkms (2.0.3-9+deb11u1)
> bullseye-backports zfs-dkms (2.1.11-1~bpo11+1)
> bookworm zfs-dkms (2.1.11-1)
> bookworm-backports zfs-dkms (2.2.2-4~bpo12+1)
> trixie zfs-dkms (2.2.2-4)
>
>
> The question is, how far back to go? Is OpenZFS 2.1.x buggy? OpenZFS
> 2.0.x? What is 0.7.12 -- OpenZFS, ZFS-on-Linux, or something else --
> and is it buggy?
This seems to be very "involved"! The discussion in #15526 suggests a coreutils upgrade (particularly re. "cp") in combination with the addition of the zpool block cloning feature seems to have triggered the issue, which may have gone undetected for some time.
>> After downgrading coreutils from 9.3 to 8.32, I am no longer able to reproduce this corruption.
> This seems to solve the corruption issue on my end too.
-- https://github.com/openzfs/zfs/issues/15526#issuecomment-1810472547
See also
https://www.reddit.com/r/zfs/comments/1826lgs/psa_its_not_block_cloning_its_a_data_corruption/
Debian users can't follow the gentoo/emerge-based reproduction/trigger steps for build of golang in
https://github.com/openzfs/zfs/issues/15526 (for zfs 2.2.0)
and
https://github.com/openzfs/zfs/issues/15933 (for 2.2.3)
If anyone can recommend steps to debianise these (15933 seem most likely to be useful, and slightly different), I would be happy to test openzfs 2.2.2-4 from bookworm-backports on deb 12.5
Given that the original gentoo reporter, who seems to have tested extensively, considered the issue closed after upgrade to openzfs 2.2.2
https://bugs.gentoo.org/917224#c26
I wonder if the 2.2.3 issue is similar/related, or perhaps there are multiple triggers.
Watching with interest.
Best wishes,
Gareth
Reply to: