On Mon, Mar 30, 2026 at 11:11 AM Thomas Munro <[email protected]> wrote: > ... so that's a yes, lseek sees holes that we didn't ask it to make,
Oops, sorry, I wrote that email too fast and got my examples mixed up, BTFS actually *doesnt* do that automatically, that was of course a trace showing a file with explicitly made holes. So this is probably be a ZFS-only issue unless you're using wal_init_zero=0, and then any file system could result in PAX-sparse-format tarballs, but even then only if you use non-default switches that in practice no one will use with GNU tar, or if you use BSD tar. So in practice this is a FreeBSD-only issue.
