From mboxrd@z Thu Jan 1 00:00:00 1970 References: <909d4cae-ddd2-3951-eee8-8dec8faa6f22@redhat.com> <8a27504b-1b3a-7126-7ade-18f57b819ead@redhat.com> From: Gionatan Danti Message-ID: <3e8184ac-4357-3b97-ac3c-d1133606f103@assyoma.it> Date: Wed, 23 Oct 2019 16:40:01 +0200 MIME-Version: 1.0 In-Reply-To: <8a27504b-1b3a-7126-7ade-18f57b819ead@redhat.com> Content-Language: en-US Content-Transfer-Encoding: quoted-printable Subject: Re: [linux-lvm] exposing snapshot block device Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="iso-8859-1"; format="flowed" To: LVM general discussion and development , Zdenek Kabelac , Ilia Zykov On 23/10/19 15:05, Zdenek Kabelac wrote: > Yep - we are recommending to disable zeroing as soon as chunksize >512K. >=20 > But for 'security' reason the option it's up to users to select what=20 > fits the needs in the best way - there is no=EF=BF=BD 'one solution fits = them=20 > all' in this case. Sure, but again: if writing a block larger than the underlying chunk,=20 zeroing can (and should) skipped. Yet I seem to remember that the new=20 block is zeroed in any case, even if it is going to be rewritten entirely. Do I remember wrongly? --=20 Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti@assyoma.it - info@assyoma.it GPG public key ID: FF5F32A8