On Thu, Oct 23, 2025 at 07:18:24PM +0200, Arsen Arsenović wrote:
"Richard W.M. Jones" <rjones(a)redhat.com> writes:
> On Thu, Oct 23, 2025 at 06:45:33PM +0200, Arsen Arsenović wrote:
>> "Richard W.M. Jones" <rjones(a)redhat.com> writes:
>>
>> > I was definitely expecting this one to fail with ENOTSUP or similar.
>> > That's with the file copy-allocated-destination-zero-synch.out on ZFS?
>>
>> Yes - my home directory is on ZoL, and so is ~/tmp.
>
> It appears this is a limitation of OpenZFS:
>
>
https://github.com/openzfs/zfs/blob/fc519b2c1108b52aaad63e356645f63c2c167...
I figured that might be the case. ZFS has a few instances of similar
issues.
In QEMU, we ended up skipping several tests on ZFS that rely on
measuring sparseness, because of the unpredictability of ZFS:
https://gitlab.com/qemu-project/qemu/-/commit/c49dda72
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization:
qemu.org |
libguestfs.org