Date: Fri, 24 Nov 2023 00:23:01 -0500 (EST) From: Chris Hill <chris@monochrome.org> To: James Miller <jimomak@os3.org> Cc: FreeBSD Questions List <questions@freebsd.org> Subject: Re: OpenZFS 2.2 -> 2.2.1 Block Cloning Bug Data Corruption Message-ID: <alpine.BSF.2.20.2311240019390.12736@tripel.monochrome.org> In-Reply-To: <be1e4010-9755-413b-804b-ab28e0a15e30@OS3> References: <86c822d2-751a-43b6-a8ee-068429b5bc24@gmx.at> <CAFYkXjkb0P71=kDfG_TFz_hi4BbmMWGm5tcWG0Y-5fVCSnEeLw@mail.gmail.com> <hn7mmi5kthzuoohneh3rmz2zxb6gsku7zkkptmnornafygfejc@563asdybzgxo> <iib7hdv4ihdwha6pkp6vkcaqxo2p5zsipzhzdrdvar6jkoma7g@4iz2zprub56t> <35b0d223-6b92-4c3e-9331-e356e6977bb0@sentex.net> <be1e4010-9755-413b-804b-ab28e0a15e30@OS3>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--273846429-906214191-1700803204=:12736
Content-Type: text/plain; CHARSET=ISO-8859-15; FORMAT=flowed
Content-Transfer-Encoding: 8BIT
Content-ID: <alpine.BSF.2.20.2311240020191.12736@tripel.monochrome.org>
Send email to the following address:
questions+unsubscribe@freebsd.org
With the subject: Unsubscribe
[ individual cc's removed ]
On Thu, 23 Nov 2023, James Miller wrote:
> Please help me. How may I unsubscribe from this email. It is flooding my email server.
>
> James Miller
> (425) 471-8101
> www.electionhope.com (http://www.electionhope.com)
> www.os3.org (http://www.os3.org)
> "If the mind is blind, the eye cannot see"
>
>
> On 2023-11-23 12:01, mike tancsa <mike@sentex.net> wrote:
>> On 11/23/2023 8:36 AM, Julien Cigar wrote:
>>> On Thu, Nov 23, 2023 at 01:07:33PM +0100, infoomatic wrote:
>>>> 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
>>> Ah, thanks for the link..! I hope an EN will be published ASAP then, it
>>> looks a serious issue..
>>
>> Am I right in reading
>> sudo sysctl -w vfs.zfs.dmu_offset_next_sync=0
>>
>> to work around the issue for now ?
>>
>> ---Mike
>>
>>
>>
>>
>
--
Chris Hill chris@monochrome.org
--273846429-906214191-1700803204=:12736--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.2311240019390.12736>