Date: Tue, 2 Jan 2024 07:49:13 +0100 From: Kurt Jaeger <pi@freebsd.org> To: Alexander Leidinger <Alexander@leidinger.net> Cc: freebsd-current@freebsd.org Subject: Re: ZFS problems since recently ? Message-ID: <ZZOx6Zuoye8pt-zl@fc.opsec.eu> In-Reply-To: <5210dd54acbaa8d7705aa4f756e21d1a@Leidinger.net> References: <ZZG0RdFTqfbfPwf7@fc.opsec.eu> <5210dd54acbaa8d7705aa4f756e21d1a@Leidinger.net>
index | next in thread | previous in thread | raw e-mail
Hi! > Am 2023-12-31 19:34, schrieb Kurt Jaeger: > > I already have > > > > vfs.zfs.dmu_offset_next_sync=0 > > > > which is supposed to disable block-cloning. > > It isn't. This one is supposed to fix an issue which is unrelated to block > cloning (but can be amplified by block cloning). This issue is fixed since > some weeks, your Dec 23 build should not need it (when the issues happens, > you have files with zero as parts of the data instead of the real data, > and only if you copy files at the same time as those files are modified, > and then only if you happen to get the timing right). > > The sysctl for block cloning is vfs.zfs.bclone_enabled. > To check if a pool has made use of block cloning: > zpool get all poolname | grep bclone Thanks. I now used that sysctl and my testcase (testbuild of shells/bash) and it did not crash. -- pi@FreeBSD.org +49 171 3101372 Now what ?home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZZOx6Zuoye8pt-zl>