1265768 – unable to swap thin meta volume residing on a shared VG

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1265768 - unable to swap thin meta volume residing on a shared VG

Summary: unable to swap thin meta volume residing on a shared VG

Keywords:
Status:	CLOSED WONTFIX
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	lvm2
Sub Component:
Version:	7.8
Hardware:	x86_64
OS:	Linux
Priority:	medium
Severity:	medium
Target Milestone:	rc
Target Release:	---
Assignee:	David Teigland
QA Contact:	cluster-qe@redhat.com
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	1686539
TreeView+	depends on / blocked

Reported:	2015-09-23 17:32 UTC by Corey Marthaler
Modified:	2021-09-03 12:53 UTC (History)
CC List:	7 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Clones:	1686539 (view as bug list)
Environment:
Last Closed:	2020-12-15 07:37:00 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Corey Marthaler 2015-09-23 17:32:34 UTC

Description of problem:
# setting up first "global lock" dummy vg for lvmlockd...
vgcreate --shared global /dev/sdd2
vgchange --lock-start global

# creating lvm devices...
pvcreate /dev/sdd1 /dev/sdb2 /dev/sdb1 /dev/sdc2 /dev/sdc1 /dev/sda2 /dev/sda1 /dev/sde2
vgcreate --shared snapper_thinp /dev/sdd1 /dev/sdb2 /dev/sdb1 /dev/sdc2 /dev/sdc1 /dev/sda2 /dev/sda1 /dev/sde2
vgchange --lock-start snapper_thinp

lvcreate  --thinpool POOL --profile thin-performance --zero n -L 1G --poolmetadatasize 4M snapper_thinp

[root@host-113 ~]# lvs -a -o +devices
  LV              VG            Attr       LSize   Pool Origin Data%  Meta% Devices
  [lvmlock]       global        -wi-ao---- 256.00m                          /dev/sdd2(0)
  POOL            snapper_thinp twi-a-t---   1.00g             0.00   0.98  POOL_tdata(0)
  [POOL_tdata]    snapper_thinp Twi-ao----   1.00g                          /dev/sdd1(65)
  [POOL_tmeta]    snapper_thinp ewi-ao----   4.00m                          /dev/sde2(0)
  [lvmlock]       snapper_thinp -wi-ao---- 256.00m                          /dev/sdd1(0)
  [lvol0_pmspare] snapper_thinp ewi-------   4.00m                          /dev/sdd1(64)

# step up for a sanity check of pool device metadata (thin_check /dev/mapper/snapper_thinp-meta_swap)
[root@host-113 ~]# lvchange -an --yes --select 'lv_name=POOL || pool_lv=POOL'
[root@host-113 ~]# lvcreate -L 4M -n meta_swap snapper_thinp
  Logical volume "meta_swap" created.
[root@host-113 ~]# lvconvert --yes --thinpool snapper_thinp/POOL --poolmetadata snapper_thinp/meta_swap
  Internal error: LV snapper_thinp/POOL_tmeta shouldn't have lock_args


Version-Release number of selected component (if applicable):
3.10.0-306.el7.x86_64

lvm2-2.02.130-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
lvm2-libs-2.02.130-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
lvm2-cluster-2.02.130-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
device-mapper-1.02.107-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
device-mapper-libs-1.02.107-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
device-mapper-event-1.02.107-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
device-mapper-event-libs-1.02.107-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
device-mapper-persistent-data-0.5.5-1.el7    BUILT: Thu Aug 13 09:58:10 CDT 2015
cmirror-2.02.130-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
sanlock-3.2.4-1.el7    BUILT: Fri Jun 19 12:48:49 CDT 2015
sanlock-lib-3.2.4-1.el7    BUILT: Fri Jun 19 12:48:49 CDT 2015
lvm2-lockd-2.02.130-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015


How reproducible:
Everytime

Comment 2 David Teigland 2015-09-24 19:08:01 UTC

I'd forgotten about that feature; it's among the "not yet implemented" features, which the error should explain.

Comment 7 RHEL Program Management 2020-12-15 07:37:00 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

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