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:05:44 +0100 [thread overview]
Message-ID: <544E0AE8.7080804@gmail.com> (raw)
In-Reply-To: <CADxRZqxDOZ4Usyp3bnWN9pvzyGD_C0tME1KGPZ1n+7mg8yoa8A@mail.gmail.com>
Dne 27.10.2014 v 07:58 Anatoly Pugachev napsal(a):
> On Sun, Oct 26, 2014 at 1:47 AM, Zdenek Kabelac <zkabelac@redhat.com
> <mailto:zkabelac@redhat.com>> wrote:
> >
> > Dne 25.10.2014 v 22:53 Vasiliy Tolstov napsal(a):
> >>
> >> 2014-10-26 0:18 GMT+04:00 Zdenek Kabelac <zkabelac@redhat.com
> <mailto:zkabelac@redhat.com>>:
> >>>
> >>> 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.
> >>
> >>
> >>
> >> I'm do dd and send it. While i'm break thin pool i'm try to restore volume
> 2657.
> >> But i don't stop lvm thin pool =(.
> >>
> >
> >
> > 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)
>
> Zdenek,
>
> can you please describe (possibly in details) what have you done with tar.gz
> sent to you, so everyone would know what to do next time?
>
> Thanks a lot!
Any Google query on lvm2 metadata recovery will disclose this - I've picked
randomly this one:
http://microdevsys.com/wp/linux-lvm-recovering-a-lost-volume/
In this case however provided data by user were just too short since he
created 300M metadata space - so I've asked to resend 4M on my email - so you
will not exactly find the info above in the initial tar.gz file (there
are just older versions) - but if you open file in 'vi' editor - you will see
those metadata yourself.
Zdenek
prev parent reply other threads:[~2014-10-27 9:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 19:59 fix corrupted thin pool Vasiliy Tolstov
2014-10-24 19:59 ` [linux-lvm] " Vasiliy Tolstov
2014-10-25 12:43 ` Zdenek Kabelac
2014-10-25 12:43 ` [linux-lvm] " Zdenek Kabelac
2014-10-25 18:41 ` Vasiliy Tolstov
2014-10-25 18:41 ` [linux-lvm] [dm-devel] " Vasiliy Tolstov
2014-10-25 18:42 ` Vasiliy Tolstov
2014-10-25 18:42 ` [linux-lvm] [dm-devel] " Vasiliy Tolstov
2014-10-25 20:18 ` Zdenek Kabelac
2014-10-25 20:18 ` [linux-lvm] [dm-devel] " Zdenek Kabelac
2014-10-25 20:53 ` Vasiliy Tolstov
2014-10-25 20:53 ` [linux-lvm] [dm-devel] " 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 [this message]
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=544E0AE8.7080804@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.