Bug 1091562 - LVM THIN: Unable to perform vgsplit when specifying thin[pool] by name
Summary: LVM THIN: Unable to perform vgsplit when specifying thin[pool] by name
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: 0-beta1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Zdenek Kabelac
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1119323
TreeView+ depends on / blocked
 
Reported: 2014-04-25 22:09 UTC by Jonathan Earl Brassow
Modified: 2021-02-02 14:02 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-02 14:02:52 UTC
Embargoed:
rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.