Date: Thu, 23 Nov 2023 13:07:33 +0100 From: infoomatic <infoomatic@gmx.at> To: questions@freebsd.org Subject: Re: OpenZFS 2.2 -> 2.2.1 Block Cloning Bug Data Corruption Message-ID: <86c822d2-751a-43b6-a8ee-068429b5bc24@gmx.at> In-Reply-To: <iib7hdv4ihdwha6pkp6vkcaqxo2p5zsipzhzdrdvar6jkoma7g@4iz2zprub56t> References: <CAFYkXjkb0P71=kDfG_TFz_hi4BbmMWGm5tcWG0Y-5fVCSnEeLw@mail.gmail.com> <iib7hdv4ihdwha6pkp6vkcaqxo2p5zsipzhzdrdvar6jkoma7g@4iz2zprub56t>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23.11.23 12:05, Julien Cigar wrote: > On Thu, Nov 23, 2023 at 02:20:49AM +0100, Tomek CEDRO wrote: >> https://www.phoronix.com/news/OpenZFS-2.2.1-Released > > Fortunately block cloning is disabled by default on 14.0-RELEASE, > (see vfs.zfs.bclone_enabled) > I would not be too sure about that, see [1]. It seems just that with this option disabled it is much harder to hit the bug. [1] https://github.com/openzfs/zfs/issues/15526#issuecomment-1823857131
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86c822d2-751a-43b6-a8ee-068429b5bc24>