1149287 – pvmove doesn't work on exclusively activated clustered thin pool volumes

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 1149287 - pvmove doesn't work on exclusively activated clustered thin pool volumes

Summary: pvmove doesn't work on exclusively activated clustered thin pool volumes

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

Reported:	2014-10-03 16:29 UTC by Corey Marthaler
Modified:	2023-03-08 07:27 UTC (History)
CC List:	7 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2020-09-09 15:15:54 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Corey Marthaler 2014-10-03 16:29:30 UTC

Description of problem:
This is just like bugs 1133149 and 1100049 but for thin pools.


[root@taft-01 ~]# vgcreate VG /dev/mapper/mpath[abcdefgh]p*
  Volume group "VG" successfully created

[root@taft-01 ~]# vgs
  VG        #PV #LV #SN Attr   VSize  VFree
  VG          8   0   0 wz--n-  1.95t 1.95t

[root@taft-01 ~]# lvcreate --thinpool POOL  --zero n -L 4G --poolmetadatasize 100M VG
  Logical volume "lvol0" created
  Logical volume "POOL" created
[root@taft-01 ~]# lvs -a -o +devices
  LV              VG  Attr       LSize   Pool Origin Data%  Meta%  Devices
  POOL            VG  twi-a-t---   4.00g             0.00   0.05   POOL_tdata(0)
  [POOL_tdata]    VG  Twi-ao----   4.00g                           /dev/mapper/mpathap1(25)
  [POOL_tmeta]    VG  ewi-ao---- 100.00m                           /dev/mapper/mpathhp1(0)
  [lvol0_pmspare] VG  ewi------- 100.00m                           /dev/mapper/mpathap1(0)

[root@taft-01 ~]# lvcreate --virtualsize 1G -T VG/POOL -n origin
  Logical volume "origin" created

[root@taft-01 ~]# lvcreate -K -s /dev/VG/origin -n snap1
  Logical volume "snap1" created

[root@taft-01 ~]# lvs -a -o +devices
  LV              VG  Attr       LSize   Pool Origin Data%  Meta%  Devices
  POOL            VG  twi-a-t---   4.00g             0.00   0.06   POOL_tdata(0)
  [POOL_tdata]    VG  Twi-ao----   4.00g                           /dev/mapper/mpathap1(25)
  [POOL_tmeta]    VG  ewi-ao---- 100.00m                           /dev/mapper/mpathhp1(0)
  [lvol0_pmspare] VG  ewi------- 100.00m                           /dev/mapper/mpathap1(0)
  origin          VG  Vwi-a-t---   1.00g POOL        0.01
  snap1           VG  Vwi-a-t--k   1.00g POOL origin 0.01

[root@taft-01 ~]# pvmove /dev/mapper/mpathap1
  /dev/mapper/mpathap1: Moved: 0.2%
  /dev/mapper/mpathap1: Moved: 2.4%
  /dev/mapper/mpathap1: Moved: 20.9%
  /dev/mapper/mpathap1: Moved: 36.1%
  /dev/mapper/mpathap1: Moved: 51.4%
  /dev/mapper/mpathap1: Moved: 71.1%
  /dev/mapper/mpathap1: Moved: 89.6%
  /dev/mapper/mpathap1: Moved: 100.0%


# When that same command is done on a clustered VG but activated exclusively pool:
[root@taft-01 ~]# pvmove /dev/mapper/mpathap1
  Skipping thin-pool LV POOL
  Skipping thin-related LV POOL_tdata
  /dev/mapper/mpathap1: Moved: 8.0%
  /dev/mapper/mpathap1: Moved: 100.0%


Version-Release number of selected component (if applicable):
2.6.32-502.el6.x86_64

lvm2-2.02.111-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
lvm2-libs-2.02.111-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
lvm2-cluster-2.02.111-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
udev-147-2.57.el6    BUILT: Thu Jul 24 08:48:47 CDT 2014
device-mapper-1.02.90-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
device-mapper-libs-1.02.90-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
device-mapper-event-1.02.90-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
device-mapper-event-libs-1.02.90-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
device-mapper-persistent-data-0.3.2-1.el6    BUILT: Fri Apr  4 08:43:06 CDT 2014
cmirror-2.02.111-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014

Comment 2 Zdenek Kabelac 2014-11-25 13:54:21 UTC

The nature of pvmove code currently requires to activate LVs on pvmoved extents, so we needs to take a special care with 'special' volumes.

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