From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Andres Toomsalu <andres@active.ee>
Subject: Re: [linux-lvm] how to recover after thin pool metadata did fill up?
Date: Thu, 18 Oct 2012 13:29:28 +0200 [thread overview]
Message-ID: <507FE818.3070009@redhat.com> (raw)
In-Reply-To: <CC9722DE-C18E-4CC7-A442-9256CCD46E2A@active.ee>
Dne 18.10.2012 12:42, Andres Toomsalu napsal(a):
> Yes I know that its not currently possible to recover this pool anymore - and we got data copied from read-only mode anyway - but bigger problem is that there is even no known way to reset/recreate pool - as I cant delete/remove the pool - which means that only erasing all PV will help probably. Im just looking for a way to erase faulty pool (with erasing data) and to be able recreate it without full OS reinstall. Is there a way to do it - DM mapper low level commands perhaps?
>
This case is pretty simple this way:
vgcfgbackup -f vg.bak vgname
edit vg.bak and remove all thinp related volumes
vgcfgrestore -f vg.bak vgname
The reason why current upstream code rather avoids modifying metadata by
tools is - to avoid making first worst for recover in the first place.
Please note we already have some work done towards removing mutliple LVs
more efficiently - https://bugzilla.redhat.com/show_bug.cgi?id=817768
Zdenek
next prev parent reply other threads:[~2012-10-18 11:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 20:21 [linux-lvm] how to recover after thin pool metadata did fill up? Andres Toomsalu
2012-10-18 10:30 ` Zdenek Kabelac
2012-10-18 10:42 ` Andres Toomsalu
2012-10-18 10:55 ` Andres Toomsalu
2012-10-18 11:29 ` Zdenek Kabelac [this message]
2012-10-18 13:28 ` Spelic
2012-10-18 13:35 ` Andres Toomsalu
2012-10-18 13:43 ` Zdenek Kabelac
2012-10-18 13:47 ` Andres Toomsalu
2012-10-18 14:01 ` Joe Thornber
2012-10-18 13:35 ` Joe Thornber
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=507FE818.3070009@redhat.com \
--to=zkabelac@redhat.com \
--cc=andres@active.ee \
--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).