Date: Sun, 3 Dec 2023 18:32:24 -0500 From: Ed Maste <emaste@freebsd.org> To: mem@schmem.com Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD Errata Notice FreeBSD-EN-23:16.openzfs Message-ID: <CAPyFy2DUXVXTSKsGe=CX5KDD0f-btRq5kbHVe312U5VPsBXkWw@mail.gmail.com> In-Reply-To: <ZWvHxOiy5VYRY63w@schorl.qozzy.net> References: <20231201031737.DF0231B942@freefall.freebsd.org> <ZWsI4SbNU2xPjaPF@marvin.hueftgold.tld> <ZWvHxOiy5VYRY63w@schorl.qozzy.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2 Dec 2023 at 19:11, Mark E. Mallett <mem@schmem.com> wrote:> > Second, it gives workaround of "vfs.zfs.dmu_offset_next_sync sysctl to 0" > But on my 12.4 systems there is no such sysctl variable. Oh, yes - the workaround is only applicable to 13.2 and later. For 12.4 there is no workaround. Note that it is much harder to encounter accidentally on 12.4, as 12.4 does not support copy_file_range(2). Applications that explicitly seek holes can encounter this issue (and it is reproducible on 12.4 via the test scripts) but it won't occur when using cp to copy on 12.4.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2DUXVXTSKsGe=CX5KDD0f-btRq5kbHVe312U5VPsBXkWw>