linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] [dm-devel] fix corrupted thin pool
Date: Mon, 27 Oct 2014 10:15:47 +0100	[thread overview]
Message-ID: <544E0D43.6010606@gmail.com> (raw)
In-Reply-To: <CACaajQtovTJHJQCh1uR7jojxyrpsjcrbO65qngyO6DvuDnYHWw@mail.gmail.com>

Dne 26.10.2014 v 20:46 Vasiliy Tolstov napsal(a):
> 2014-10-26 2:47 GMT+04:00 Zdenek Kabelac <zkabelac@redhat.com>:
>>  From the metadata  something bad was going one:
>>
>> Fri Oct 24 17:03:04 2014
>>
>> transaction_id = 120  - create = "3695"
>>
>> And suddenly on Fri Oct 24 18:07:23 2014
>> pool is back on older transaction_id
>>
>> transaction_id = 114
>>
>>
>> Is that the time of your vgcfgrestore?
>>
>> I'm attaching those metadata which you likely should put back to get in sync
>> with your kernel metadata (assuming you have not modified those in any way)
>
>
> Hm yes, i miss that one vg created in this time, thanks. As i
> understand transaction id needs to be changed? Or something other?
> But i have error:
>
> lvchange -ay vg1/2735
>    Check of thin pool vg1/tp1 failed (status:1). Manual repair required
> (thin_dump --repair /dev/mapper/vg1-tp1_tmeta)!
>


If you would have latest lvm2 tools - you could have tried:

lvconvert --repair  vg/pool


With older tools - you need to go in these manual step:


1. create temporary small LV
# lvcreate -an -Zn -L10 --name temp vg

2. replace pool's metadata volume with this tempLV
# lvconvert --thinpool vg/pool  --poolmetadata temp
(say 'y' to swap)

3. activate & repair metadata from 'temp' volume - you will likely need 
another volume where to store repaire metadata -
so create:
# lvcreate -Lat_least_as_big_as_temp  --name repaired  vg
# lvchage -ay vg/temp
# thin_repair -i /dev/vg/temp  /dev/vg/repaired

if everything when fine - compare visualy 'transaction_id' of repaired 
metadata  (thin_dump /dev/vg/repaired)

4. swap deactivated repaired volume back to your thin-pool
# lvchange -an vg/repaired
# lvconvert --thinpool vg/pool --poolmetadata repaired

try to activate pool -  if it doesn't work report more problems.

Zdenek

  reply	other threads:[~2014-10-27  9:15 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
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 [this message]
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=544E0D43.6010606@gmail.com \
    --to=zdenek.kabelac@gmail.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).