Bug 1114068

Summary:	"Internal error: Performing unsafe table load" error during snapshot of cache origin volume removal
Product:	Red Hat Enterprise Linux 6	Reporter:	Corey Marthaler <cmarthal>
Component:	lvm2	Assignee:	Zdenek Kabelac <zkabelac>
lvm2 sub component:	Cache Logical Volumes (RHEL6)	QA Contact:	Cluster QE <mspqa-list>
Status:	CLOSED DEFERRED	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	agk, heinzm, jbrassow, mcsontos, msnitzer, prajnoha, zkabelac
Version:	6.6
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1091553	Environment:
Last Closed:	2014-08-27 12:55:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1091553
Bug Blocks:

Comment 1 Corey Marthaler 2014-06-27 16:00:11 UTC

[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 2 Jonathan 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.

Comment 3 Marian Csontos 2014-08-27 12:55:37 UTC

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.