Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
[root@host-001 ~]# lvs -a -o +devices
LV Attr LSize Pool Origin Data% Devices
corigin owi-a-C--- 4.00g fs_A_pool [corigin_corig] corigin_corig(0)
[corigin_corig] -wi-ao---- 4.00g /dev/sda1(0)
fs_A_pool Cwi---C--- 2.00g fs_A_pool_cdata(0)
[fs_A_pool_cdata] Cwi-aoC--- 2.00g /dev/sdh1(0)
[fs_A_pool_cmeta] ewi-aoC--- 8.00m /dev/sdh1(512)
fs_snap1 swi-a-s--- 500.00m corigin 0.00 /dev/sdh1(516)
fs_snap2 swi-a-s--- 500.00m corigin 0.00 /dev/sdh1(641)
fs_snap3 swi-a-s--- 500.00m corigin 0.00 /dev/sdh1(766)
fs_snap4 swi-a-s--- 500.00m corigin 0.00 /dev/sdh1(891)
fs_snap5 swi-a-s--- 500.00m corigin 0.00 /dev/sdh1(1016)
[lvol0_pmspare] ewi------- 8.00m /dev/sdh1(514)
[root@host-001 ~]# lvremove cache_sanity/fs_snap1
Do you really want to remove active logical volume fs_snap1? [y/n]: y
Internal error: Performing unsafe table load while 9 device(s) are known to be suspended: (253:7)
Logical volume "fs_snap1" successfully removed
[root@host-001 ~]# lvremove -f cache_sanity/fs_snap2
Internal error: Performing unsafe table load while 7 device(s) are known to be suspended: (253:7)
Logical volume "fs_snap2" successfully removed
[root@host-001 ~]# lvremove -f cache_sanity/fs_snap3
Internal error: Performing unsafe table load while 5 device(s) are known to be suspended: (253:7)
Logical volume "fs_snap3" successfully removed
[root@host-001 ~]# lvremove -f cache_sanity/fs_snap4
Internal error: Performing unsafe table load while 3 device(s) are known to be suspended: (253:7)
Logical volume "fs_snap4" successfully removed
[root@host-001 ~]# lvremove -f cache_sanity/fs_snap5
Logical volume "fs_snap5" successfully removed
2.6.32-485.el6.x86_64
lvm2-2.02.107-1.el6 BUILT: Mon Jun 23 09:44:45 CDT 2014
lvm2-libs-2.02.107-1.el6 BUILT: Mon Jun 23 09:44:45 CDT 2014
lvm2-cluster-2.02.107-1.el6 BUILT: Mon Jun 23 09:44:45 CDT 2014
udev-147-2.55.el6 BUILT: Wed Jun 18 06:30:21 CDT 2014
device-mapper-1.02.86-1.el6 BUILT: Mon Jun 23 09:44:45 CDT 2014
device-mapper-libs-1.02.86-1.el6 BUILT: Mon Jun 23 09:44:45 CDT 2014
device-mapper-event-1.02.86-1.el6 BUILT: Mon Jun 23 09:44:45 CDT 2014
device-mapper-event-libs-1.02.86-1.el6 BUILT: Mon Jun 23 09:44:45 CDT 2014
device-mapper-persistent-data-0.3.2-1.el6 BUILT: Fri Apr 4 08:43:06 CDT 2014
cmirror-2.02.107-1.el6 BUILT: Mon Jun 23 09:44:45 CDT 2014
Comment 2Jonathan Earl Brassow
2014-08-27 12:34:15 UTC
Moving this bug to rhel6.7 for the following reasons:
1) Cannot be a blocker for 6.6 release because cache is in tech preview
2) snapshots of cache LVs have been disabled for this release, so it is likely not possible to hit this bug now.
Snapshots of cache devices are now disabled. The FutureFeature is tracked as Bug 1133101. Closing as deferred.
We may still need a way to clean up the VG - see Bug 1114151#c2.