From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zdenek Kabelac Subject: Re: Reducing size of thin spare metadata, thin metadata Date: Mon, 06 Oct 2014 10:57:27 +0200 Message-ID: <54325977.9090805@redhat.com> References: <54324732.5080107@redhat.com> <54324D57.1050704@redhat.com> <5432534A.5090409@redhat.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; Format="flowed" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: patrik@dsl.sk Cc: device-mapper development List-Id: dm-devel.ids Dne 6.10.2014 v 10:48 Patrik Horn=EDk napsal(a): > Thanks Zdenku. But you did not answer some of my questions, which I > need to know to decide... So is there a way I can create smaller spare > metadata LV? In mentioned manual steps what do I need mytemplv for and > why cant I use original pool metadata as input of thin_repair? Spare volume is maintained to have the size at least as the biggest pool metadata volume in VG. There is no point to keep smaller reserved space. We do not allow to activate 'subvolumes' - thus you cannot activate just 'thin pool metadata' - that's why you need to swap _tmeta out thin pool. Zdenek