Bug 1091562

Summary: LVM THIN: Unable to perform vgsplit when specifying thin[pool] by name
Product: [Community] LVM and device-mapper Reporter: Jonathan Earl Brassow <jbrassow>
Component: lvm2Assignee: Zdenek Kabelac <zkabelac>
lvm2 sub component: Command-line tools QA Contact: cluster-qe <cluster-qe>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: unspecified    
Priority: unspecified CC: agk, coughlan, heinzm, jbrassow, msnitzer, prajnoha, rbednar, thornber, zkabelac
Version: 0-beta1Flags: rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-02 14:02:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1119323    

Description Jonathan Earl Brassow 2014-04-25 22:09:11 UTC
When I was looking at bug 875930, I tried a couple tests with thin[pool] to see if it worked with vgsplit (https://bugzilla.redhat.com/show_bug.cgi?id=875930#c6).  Here is what I found:

<comment_6>
I thought this bug would affect thin-p also, since it is possible to put data and metadata on the same device.  However, the code ignores the thin pool metadata device in that case and it works when everything is on the same device.  However, when thin-p sub-LVs are on different devices (i.e. the normal case), it doesn't work:

[root@bp-01 ~]# vgsplit -n thin_pool vg vg_new
  Can't split pool data and metadata thin_pool between two Volume Groups.
[root@bp-01 ~]# vgsplit -n thin_lv vg vg_new
  Cannot split: Nowhere to store metadata for new Volume Group

Probably a separate bug for that.  I'm sure it works fine if just PVs are specified.
</comment_6>

Comment 7 Zdenek Kabelac 2021-02-02 14:02:52 UTC
This works for many years already (fixed in 2016).