From nobody Fri Nov 24 10:37:50 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4ScBJc6jK6z52Jf2 for ; Fri, 24 Nov 2023 10:37:52 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from mail.flex-it.com.ua (mail.flex-it.com.ua [193.239.74.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4ScBJc37cyz4Rcn for ; Fri, 24 Nov 2023 10:37:52 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of shuriku@shurik.kiev.ua designates 193.239.74.7 as permitted sender) smtp.mailfrom=shuriku@shurik.kiev.ua; dmarc=none Received: from [188.231.181.61] (helo=[10.2.1.104]) by mail.flex-it.com.ua with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.96.2 (FreeBSD)) (envelope-from ) id 1r6TZG-000Jf7-31 for freebsd-current@freebsd.org; Fri, 24 Nov 2023 12:37:50 +0200 Message-ID: Date: Fri, 24 Nov 2023 12:37:50 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: openzfs and block cloning question Content-Language: uk-UA To: freebsd-current@freebsd.org References: <17265de6-fcbb-4154-adbd-4c56552b747d@shurik.kiev.ua> <25dab6bbc32f85ac710535776cd9d376@Leidinger.net> From: Oleksandr Kryvulia In-Reply-To: <25dab6bbc32f85ac710535776cd9d376@Leidinger.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-ACL-Warn: SPF failed. 188.231.181.61 is not allowed to send mail from shurik.kiev.ua. X-Spamd-Result: default: False [-2.38 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; R_SPF_ALLOW(-0.20)[+mx:c]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-0.09)[-0.088]; XM_UA_NO_VERSION(0.01)[]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:35297, ipnet:193.239.72.0/22, country:UA]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[shurik.kiev.ua]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4ScBJc37cyz4Rcn X-Spamd-Bar: -- 24.11.23 10:17, Alexander Leidinger: > Am 2023-11-24 08:10, schrieb Oleksandr Kryvulia: >> Hi, >> Recently cperciva@ published in his twitter [1] that enabling block >> cloning feature tends to data lost on 14.  Is this statement true for >> the current? Since I am using current for daily work and block >> cloning enabled by default how can I verify that my data is not >> affected? >> Thank you. > > Block cloning may have an issue, or it does things which amplifies an > old existing issue, or there are two issues... > The full story is at >     https://github.com/openzfs/zfs/issues/15526 > > To be on the safe side, you may want to have > vfs.zfs.dmu_offset_next_sync=0 (loader.conf / sysctl.conf) for the > moment. Thanks for clarification!