Date: Mon, 31 May 2021 18:57:44 +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-1XH0LL2pbS@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 #18 from J=C3=B6rg Schilling <schily@schily.net> --- Please note that the apparent sparse files are not created on the basic system that identifies as aarch64. If I compile schilytools in an armv7 jail that runs on the aarch64 raspi installation, only some of the binaries linked for armv7 are identified as apparent sparse files. So it seems that there are some unknown constraints that trigger the problem. My guess is that the absence of an apparent problem on a different platform does not verify that the problem has been fixed. In special since the=20 affected files are linker output that depends on the platform. Since the change in nullfs is only one line, Robert can you compile a modified kernel? --=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-1XH0LL2pbS>