From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <544B9ADD.6040607@redhat.com> Date: Sat, 25 Oct 2014 14:43:09 +0200 From: Zdenek Kabelac MIME-Version: 1.0 References: In-Reply-To: Content-Transfer-Encoding: 7bit Subject: Re: [linux-lvm] fix corrupted thin pool 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="us-ascii"; format="flowed" To: device-mapper development , LVM Dne 24.10.2014 v 21:59 Vasiliy Tolstov napsal(a): > Hello! By mistake i'm restore by vcfgrestore thin volume, after that i > have errors on this thin pool on all volumes like : > lvchange -ay vg1/2735 > Thin pool transaction_id=120, while expected: 114. > Does it possible to recovery from this? I'm try lvconvert --recover > and get tp1_tmeta0 but i'm don't understand whan i need to do next..? > > Hi I'm not sure how you could do that 'by a mistake' since LVM is printing pretty BIG WARNING that any vgcfgrestore with thin should be done after big thinking and requires even extra --force option. But anyway - if you have /etc/lvm/archive - you should probably be able to find the 'right' version of lvm2 metadata for your kernel metadata. However 'normally' you could be off the sequence number only by one! so I'm quite curious what you've been able to make such big difference. If you could - package /etc/lvm/archive so I could get closer look where the lvm2 has holes to allow such operations ? Which version of lvm2 and kernel is here in use ? Have you been manipulating with thin-pool's metadata in any way ? Regards Zdenek