References: From: Zdenek Kabelac Message-ID: Date: Thu, 17 Sep 2020 21:17:58 +0200 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Transfer-Encoding: quoted-printable Subject: Re: [linux-lvm] lvm limitations 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 , =?UTF-8?Q?Tomas_Dalebj=c3=b6rk?= , Gionatan Danti Cc: Zdenek Kabelac Dne 16. 09. 20 v 6:58 Tomas Dalebj=C3=B6rk napsal(a): > just curious about this: >=20 >> Worth to note there is fixed strict limit of the ~16GiB maximum >> thin-pool kernel metadata size - which surely can be exhausted - >> mapping holds info about bTree mappings and sharing chunks between >> devices.... > would that mean that one single thin-pool can maximum hold 16GiB/16 nr of= blocks? thin_metadata_size is the tool that you can play with and see the needed sp= ace=20 of metadata to handle various sized of data volumes. The bigger the thin-pool chunk is - the less metadata is needed - but the less 'efficient' snapshot becomes. > and how about if LVM2 uses VDO as backend, are there more limitations tha= t I need to consider there that are not reflected here certainly yes - you need to check documentation for VDO how to configure=20 parameters to held given expected amount of data (with lvm lot of them is ATM configurable from lvm.conf or profiles) Zdenek