[Bug 256205] lseek() with SEEK_HOLE some times wrongly reports holes on ZFS

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 29 May 2021 21:12:09 UTC

--- Comment #4 from Jörg Schilling <schily@schily.net> ---
Does this only happen with a clone or also with a snapshot?

Since a clone is writable, it is expected to contain a copy of the
node instead of a reference to it that is used with a snapshot.

It would be interesting to know why some of the access operations (e.g
for a vanilla read) work to deliver correct content but other 
operations fail.

BTW: I just created a simple sparse file using echo and dd that does not
seem to be affected by the problem. So it seems to be a zfs bug that
is triggered by the specific way the linker did write the file that
is affected.

This is how I created the simple sparse:

      echo 123 > bla
      dd if=Makefile conv=notrunc oseek=32k of=bla

You are receiving this mail because:
You are the assignee for the bug.