Control: forwarded -1 https://github.com/folbricht/desync/issues/353
Hi Mathias, On Tue, 26 May 2026 02:06:24 +0000 Mathias Gibbens <[email protected]> wrote: > Source: desync > Version: 1.0.1-1 > Tags: sid ftbfs > > I perform most of my Debian development work in unprivileged Incus > containers with ZFS for their underlying storage. In such setups, > several of desync's tests fail in a similar way: > ... snip ... > > I'm unsure if the desync binary is also similarly broken when run in > an environment using ZFS storage. Performing the build in an identical > setup with ext4-backed storage works, so I'm not reporting this as an > RC bug. I wonder how I could reproduce this ? I guess I could setup a virtual machine with ZFS-backed storage. I've never played with ZFS, so not entirely sure what I am talking about here really. For completeness, can you confirm the version of ZFS you are using ? I assume it'll be the latest zfs-dkms (2.4.2-2) ? In any case, I've forwarded the bug upstream to see if they have any bright ideas. I guess one quick thing you could do is to try to run the latest upstream test suite on ZFS and see if you get the same issue. That could rule out any upstream fixes. You could do that with the Go libraries the project specifies, that could rule out any difference in library version as well. Cheers! Chris
