archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <>
	LVM general discussion and development <>
Subject: Re: [linux-lvm] thinpool metadata got way too large, how to handle?
Date: Fri, 10 Jan 2020 17:51:18 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Dne 10. 01. 20 v 17:30 Ede Wolf napsal(a):
> Hello,
> I am afraid I have been a bit too optimistic. Being a bit embarassed, but I am 
> not not able to find any reference to component activation. I've deactivated 
> all LVs and tried to set the thinpool itself or its metadata into read only mode:
> # lvchange -pr VG_Raid6/ThinPoolRaid6
>  � Command on LV VG_Raid6/ThinPoolRaid6 uses options invalid with LV type 
> thinpool.
>  � Command not permitted on LV VG_Raid6/ThinPoolRaid6.
> # lvchange -pr /dev/mapper/VG_Raid6-ThinPoolRaid6_tmeta
>  � Operation not permitted on hidden LV VG_Raid6/ThinPoolRaid6_tmeta.
> I can lvchange -an the thinpool, but then obviously I have no path/file for 
> for the thin_repair input anynmore that I could provide.
> So please, how do I properly set the metadata into read only?

Your lvm2 is too old   (component activation is relatively new feature)

In this case you need to simply 'swap-out'  your existing _tmeta into a 
regular LV.

Easy to do -

Just create any LV you want -   lvcreate -an -L1 -n mytestlv vg

then 'swap' content of _tmeta with mytestvl  with:

lvconvert --thinpool  vg/poolname  --poolmetadata  vg/mytestlv

and now  vg/mytestlv should be you 2.2TiB metadata volume you can easily activate.



      reply	other threads:[~2020-01-10 16:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02 18:19 [linux-lvm] thinpool metadata got way too large, how to handle? Ede Wolf
2020-01-08 11:29 ` Zdenek Kabelac
2020-01-08 14:23   ` Ede Wolf
2020-01-10 16:30   ` Ede Wolf
2020-01-10 16:51     ` Zdenek Kabelac [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).