On Tue, 15 Sep 2020 at 09:43:28 +0200, Holger Schröder wrote:
> I have found the reason for this. I had already set atime=off in my
> zpools some time ago. I tried to switch it on again (zfs set atime=on
> $pool). And the problem disappeared and everything works again.
Thanks, I can now reproduce this with "zfs set atime=on pool1" and
"gio copy x y" where x is an empty file on the ZFS volume. I had
previously tried "mount -o remount,noatime", which would have worked
with other filesystems, but apparently that doesn't work with ZFS.
> why the newer glib can't handle it I don't know
Because it uses a newer file-information API that indicates when
information from the filesystem is meaningless (like the atime on a
noatime filesystem), and the code to use that API assumes that all the
information traditionally provided by stat() is meaningful, which is a
wrong assumption on a noatime ZFS volume.
smcv
