Date: Sat, 29 May 2021 21:12:09 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 256205] lseek() with SEEK_HOLE some times wrongly reports holes on ZFS Message-ID: <bug-256205-227-QMIc1nS5qG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256205-227@https.bugs.freebsd.org/bugzilla/> References: <bug-256205-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256205 --- Comment #4 from J=C3=B6rg 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=20 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=3DMakefile conv=3Dnotrunc oseek=3D32k of=3Dbla --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256205-227-QMIc1nS5qG>