Re: OpenZFS 2.2 -> 2.2.1 Block Cloning Bug Data Corruption

From: Chris Hill <chris_at_monochrome.org>
Date: Fri, 24 Nov 2023 05:23:01 UTC 
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