From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <544C05A2.8090004@redhat.com> Date: Sat, 25 Oct 2014 22:18:42 +0200 From: Zdenek Kabelac MIME-Version: 1.0 References: <544B9ADD.6040607@redhat.com> In-Reply-To: Content-Transfer-Encoding: 7bit Subject: Re: [linux-lvm] [dm-devel] 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 Cc: LVM Dne 25.10.2014 v 20:41 Vasiliy Tolstov napsal(a): > 2014-10-25 16:43 GMT+04:00 Zdenek Kabelac : >> 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 > > > I can't provide old archive data =(, Now i only have this error.. > Also in lvm conf i have issue_discards =1 There is 'internal' metadata archive then - dd if=/dev/your_pv_volume of=/tmp/1st.megabyte bs=1M count=1 It's will capture first megabyte of your PV where are embedded metadata of your Volume group. If you are not skilled enough - tar.gz and send this file to me. Zdenek