linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Joe Thornber <thornber@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] how to recover after thin pool metadata did fill up?
Date: Thu, 18 Oct 2012 14:35:24 +0100	[thread overview]
Message-ID: <20121018133523.GA24912@ubuntu> (raw)
In-Reply-To: <CB12DB70-5C4F-4936-9EDE-BFF4096D064F@active.ee>

On Wed, Oct 17, 2012 at 11:21:35PM +0300, Andres Toomsalu wrote:
> Hi,
> 
> I'm aware that thin provisioning is not yet production ready (no metadata resize) - but is there a way to recover from thin pool failure when pool metadata was filled up?

We don't support online resizing yet.  But you can do this offline by following these rough steps:

i) dump your metadata device to a text file using thin_dump.  You may 
   want to eyeball this to see if it's what you expect.

ii) Create a new metadata lv.  Better to create a completely new one
    than try and extend the old one and risk losing data if you make a
    mistake.

iii) Use thin_restore to write the dump to the new metadata volume

iv) Tell lvm to use the new metadata area for your pool.  I'm not sure how to do this last step.  Kabi can you help please?

- Joe

      parent reply	other threads:[~2012-10-18 13:35 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
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 [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=20121018133523.GA24912@ubuntu \
    --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 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).