Date: Sat, 25 Nov 2023 09:20:22 +0000 From: Graham Perrin <grahamperrin@gmail.com> To: questions@freebsd.org Subject: openzfs/zfs issue #15526 (was: OpenZFS 2.2 -> 2.2.1 Block Cloning Bug Data Corruption) Message-ID: <56b5458c-eb4f-4f65-9d0c-8e49301523fe@gmail.com> In-Reply-To: <35b0d223-6b92-4c3e-9331-e356e6977bb0@sentex.net> References: <CAFYkXjkb0P71=kDfG_TFz_hi4BbmMWGm5tcWG0Y-5fVCSnEeLw@mail.gmail.com> <iib7hdv4ihdwha6pkp6vkcaqxo2p5zsipzhzdrdvar6jkoma7g@4iz2zprub56t> <86c822d2-751a-43b6-a8ee-068429b5bc24@gmx.at> <hn7mmi5kthzuoohneh3rmz2zxb6gsku7zkkptmnornafygfejc@563asdybzgxo> <35b0d223-6b92-4c3e-9331-e356e6977bb0@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/23/23 20:01, mike tancsa wrote: > … > > Am I right in reading > sudo sysctl -w vfs.zfs.dmu_offset_next_sync=0 > > to work around the issue for now ? No, not according to recent observations. <https://old.reddit.com/r/freebsd/comments/182pgki/-/>; has key points, including a link to Bugzilla. Email is difficult for me recently, so (please) don't expect me to answer questions on any mail list. Thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56b5458c-eb4f-4f65-9d0c-8e49301523fe>