1280450 – should a raid volume converted to a thin lv with an external origin lose its Cpy%Sync?

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 1280450 - should a raid volume converted to a thin lv with an external origin lose its Cpy%Sync?

Summary: should a raid volume converted to a thin lv with an external origin lose its ...

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

Reported:	2015-11-11 18:38 UTC by Corey Marthaler
Modified:	2021-09-03 12:55 UTC (History)
CC List:	8 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2020-12-15 07:38:23 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Corey Marthaler 2015-11-11 18:38:24 UTC

Description of problem:
This may be expected behavior, but even read only raid volumes maintain their current sync percentage.

[root@host-109 ~]# lvcreate -m 1 -n raid --type raid1 -L 100M black_bird
  Logical volume "raid" created.
[root@host-109 ~]# lvs -a -o +devices
  LV              VG          Attr       LSize   Pool Origin Data%  Meta% Cpy%Sync Devices
  raid            black_bird  rwi-a-r--- 100.00m                          100.00   raid_rimage_0(0),raid_rimage_1(0)
  [raid_rimage_0] black_bird  iwi-aor--- 100.00m                                   /dev/sda1(1)
  [raid_rimage_1] black_bird  iwi-aor--- 100.00m                                   /dev/sdb1(1)
  [raid_rmeta_0]  black_bird  ewi-aor---   4.00m                                   /dev/sda1(0)
  [raid_rmeta_1]  black_bird  ewi-aor---   4.00m                                   /dev/sdb1(0)

[root@host-109 ~]# lvcreate --type thin-pool -n POOL -L 500M black_bird /dev/sdd1
  Logical volume "POOL" created.
[root@host-109 ~]# lvs -a -o +devices
  LV              VG          Attr       LSize   Pool Origin Data%  Meta% Cpy%Sync Devices
  POOL            black_bird  twi-a-tz-- 500.00m             0.00   0.88           POOL_tdata(0)
  [POOL_tdata]    black_bird  Twi-ao---- 500.00m                                   /dev/sdd1(1)
  [POOL_tmeta]    black_bird  ewi-ao----   4.00m                                   /dev/sdd1(126)
  [lvol0_pmspare] black_bird  ewi-------   4.00m                                   /dev/sdd1(0)
  raid            black_bird  rwi-a-r--- 100.00m                          100.00   raid_rimage_0(0),raid_rimage_1(0)
  [raid_rimage_0] black_bird  iwi-aor--- 100.00m                                   /dev/sda1(1)
  [raid_rimage_1] black_bird  iwi-aor--- 100.00m                                   /dev/sdb1(1)
  [raid_rmeta_0]  black_bird  ewi-aor---   4.00m                                   /dev/sda1(0)
  [raid_rmeta_1]  black_bird  ewi-aor---   4.00m                                   /dev/sdb1(0)


# Sync percent status is now gone:
[root@host-109 ~]# lvconvert --thinpool black_bird/POOL --originname raidextorig -T raid --yes
  Logical volume "raidextorig" created.
  Converted black_bird/raid to thin volume with external origin black_bird/raidextorig.
[root@host-109 ~]# lvs -a -o +devices
  LV                     VG          Attr       LSize   Pool Origin      Data%  Meta% Cpy%Sync Devices
  POOL                   black_bird  twi-aotz-- 500.00m                  0.00   0.98           POOL_tdata(0)
  [POOL_tdata]           black_bird  Twi-ao---- 500.00m                                        /dev/sdd1(1)
  [POOL_tmeta]           black_bird  ewi-ao----   4.00m                                        /dev/sdd1(126)
  [lvol0_pmspare]        black_bird  ewi-------   4.00m                                        /dev/sdd1(0)
  raid                   black_bird  Vwi-a-tz-- 100.00m POOL raidextorig 0.00
  raidextorig            black_bird  ori---r--- 100.00m                                        raidextorig_rimage_0(0),raidextorig_rimage_1(0)
  [raidextorig_rimage_0] black_bird  Iwi-aor-r- 100.00m                                        /dev/sda1(1)
  [raidextorig_rimage_1] black_bird  Iwi-aor-r- 100.00m                                        /dev/sdb1(1)
  [raidextorig_rmeta_0]  black_bird  ewi-aor-r-   4.00m                                        /dev/sda1(0)



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

lvm2-2.02.130-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
lvm2-libs-2.02.130-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
lvm2-cluster-2.02.130-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-1.02.107-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-libs-1.02.107-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-event-1.02.107-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-event-libs-1.02.107-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015
device-mapper-persistent-data-0.5.5-1.el7    BUILT: Thu Aug 13 09:58:10 CDT 2015
cmirror-2.02.130-5.el7    BUILT: Wed Oct 14 08:27:29 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-5.el7    BUILT: Wed Oct 14 08:27:29 CDT 2015

Comment 6 RHEL Program Management 2020-12-15 07:38:23 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.