From: Zdenek Kabelac <zkabelac@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: LVM <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] [dm-devel] fix corrupted thin pool
Date: Sat, 25 Oct 2014 22:18:42 +0200 [thread overview]
Message-ID: <544C05A2.8090004@redhat.com> (raw)
In-Reply-To: <CACaajQsG+2hPqp93yU77TBTOwy2EA_zHbV=pNqiq8dpsqPXzfw@mail.gmail.com>
Dne 25.10.2014 v 20:41 Vasiliy Tolstov napsal(a):
> 2014-10-25 16:43 GMT+04:00 Zdenek Kabelac <zkabelac@redhat.com>:
>> 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
next prev parent reply other threads:[~2014-10-25 20:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 19:59 [linux-lvm] fix corrupted thin pool Vasiliy Tolstov
2014-10-25 12:43 ` Zdenek Kabelac
2014-10-25 18:41 ` [linux-lvm] [dm-devel] " Vasiliy Tolstov
2014-10-25 18:42 ` Vasiliy Tolstov
2014-10-25 20:18 ` Zdenek Kabelac [this message]
2014-10-25 20:53 ` Vasiliy Tolstov
2014-10-25 22:47 ` Zdenek Kabelac
2014-10-26 19:46 ` Vasiliy Tolstov
2014-10-27 9:15 ` Zdenek Kabelac
2014-10-28 13:55 ` Vasiliy Tolstov
2014-10-28 14:09 ` Joe Thornber
2014-10-28 14:29 ` Vasiliy Tolstov
2014-10-27 6:58 ` Anatoly Pugachev
2014-10-27 9:05 ` Zdenek Kabelac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=544C05A2.8090004@redhat.com \
--to=zkabelac@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).