All of lore.kernel.org
 help / color / mirror / Atom feed
From: Spelic <spelic@shiftmail.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Andres Toomsalu <andres@active.ee>, Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] how to recover after thin pool metadata did fill up?
Date: Thu, 18 Oct 2012 15:28:17 +0200	[thread overview]
Message-ID: <508003F1.8090308@shiftmail.org> (raw)
In-Reply-To: <507FDA2E.8080301@redhat.com>

On 10/18/12 12:30, Zdenek Kabelac wrote:
> Dne 17.10.2012 22:21, Andres Toomsalu napsal(a):
>> 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?
>>
>>
>
>
> Unfortunately there is no 'easy' advice for now yet - you hit current 
> Achilles heel of thinp support in lvm2 - we are thinking how to make 
> recovery usable for user - but it's not easy task since many things 
> are making it very complex - so it still needs some month of work.
>

So, supposing one is aware of this problem beforehand, at pool creation
can this problem be worked around by using --poolmetadatasize  to make a 
metadata volume much larger than the default?

And if yes, do you have any advice on the metadata size we should use?

Thank you

  parent reply	other threads:[~2012-10-18 13:28 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 [this message]
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=508003F1.8090308@shiftmail.org \
    --to=spelic@shiftmail.org \
    --cc=andres@active.ee \
    --cc=linux-lvm@redhat.com \
    --cc=zkabelac@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.