All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: patrik@dsl.sk
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: Reducing size of thin spare metadata, thin metadata
Date: Mon, 06 Oct 2014 09:39:30 +0200	[thread overview]
Message-ID: <54324732.5080107@redhat.com> (raw)
In-Reply-To: <CAAOsTSmgp892H5M4+XLXSQ-H3G_HFUsnykiyjW+MbP4r7U8+Qw@mail.gmail.com>

Dne 6.10.2014 v 09:28 Patrik Horník napsal(a):
> Hi,
>
> is it possible to (safely) reduce size of thin metadata and / or thin
> spare metadata? What size of spare metadata is needed? Can it be
> smaller than size of pool metadata?
>

You could remove pool spare volume anytime  - lvremove.
(it's only used for automated lvconvert --repair)

Repair needs free space in VG - if there is no free space - well tool can't be 
used.

You could also reduce size of thin pool metadata in case it's too big, just 
not online.


With offline thinpool with these manual steps
(will be later automated with tool as well):

--

make a temporary LV of any size.
swap this temp LV with  pool metadata

# lvconvert --thinpool  vg/mypool   --poolmetadata mytemplv

Create your volume for metadata with new reduced size
(unsure which size is your target - but some calcs based on estimated usage 
are necessary)

Activate   mytemplv  which has now real metadata from thinpool.

# thin_repair  -i /dev/vg/mytemplv   -o /dev/vg/mynewsizemeta

# thin_check  /dev/vg/mynewsizemeta


If all is green - swap new meta into your thinpool

# lvconvert --thinpool  vg/mypool   --poolmetadata mynewsizemeta


If all works great you are done :)
In all other cases you have your backup at hand :)

Yeah - you still have old metadata in mytemplv - this volume you may remove
later if all works well - otherwise you may try to swap this volume back.

Zdenek

  reply	other threads:[~2014-10-06  7:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06  7:28 Reducing size of thin spare metadata, thin metadata Patrik Horník
2014-10-06  7:39 ` Zdenek Kabelac [this message]
2014-10-06  7:59   ` Patrik Horník
2014-10-06  8:05     ` Zdenek Kabelac
2014-10-06  8:12       ` Patrik Horník
2014-10-06  8:31         ` Zdenek Kabelac
2014-10-06  8:48           ` Patrik Horník
2014-10-06  8:57             ` Zdenek Kabelac
     [not found]               ` <CAAOsTS=j1mUA+caJ35ChDvpQJTu2m8OHVPCEZFTJHdn9cgdhsw@mail.gmail.com>
2014-10-06  9:05                 ` Fwd: " Patrik Horník
2014-10-07  7:17                   ` Marian Csontos

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=54324732.5080107@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=patrik@dsl.sk \
    /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.