From: Joe Thornber <thornber@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] [dm-devel] fix corrupted thin pool
Date: Tue, 28 Oct 2014 14:09:06 +0000 [thread overview]
Message-ID: <20141028140905.GA16396@debian> (raw)
In-Reply-To: <CACaajQtS00j9wwTXePVA5qi3cb9PwXDukVnPktxZGOR_XtFAdQ@mail.gmail.com>
On Tue, Oct 28, 2014 at 05:55:12PM +0400, Vasiliy Tolstov wrote:
> thin_dump --repair /dev/mapper/vg1-tp1_tmeta0
thin_dump spits just spits out xml, it doesn't change the device it's
reading. So the process is either:
thin_dump --repair <dev> > metadata.xml
thin_restore -i metadata.xml -o <dev>
or you can use the thin_repair tool which does both of these
processes.
> <superblock uuid="" time="27" transaction="120" data_block_size="128"
> nr_data_blocks="7290880">
> </superblock>
This is worrying, you seem to have no volumes in your pool?
next prev parent reply other threads:[~2014-10-28 14:09 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 [this message]
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=20141028140905.GA16396@debian \
--to=thornber@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 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.