1270404 – cmd to deactivate failed cache volume hangs

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 1270404 - cmd to deactivate failed cache volume hangs

Summary: cmd to deactivate failed cache volume hangs

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:	low
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-10-09 23:22 UTC by Corey Marthaler
Modified:	2021-09-03 12:51 UTC (History)
CC List:	6 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2020-12-15 07:37:40 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Corey Marthaler 2015-10-09 23:22:26 UTC

Description of problem:
I'm looking for a way to verify bug 1189051 without any luck and came across this deactivation attempt which should probably return.


[root@host-109 ~]# lvs -a -o +devices
  LV              VG            Attr       LSize   Pool   Origin          Data%  Meta%  Move Log Cpy%Sync Devices                  
  [POOL]          cache_sanity  Cwi---C---   2.00g                        0.00   3.47            100.00   POOL_cdata(0)            
  [POOL_cdata]    cache_sanity  Cwi-ao----   2.00g                                                        /dev/sdb1(0),/dev/sdd1(0)
  [POOL_cmeta]    cache_sanity  ewi-ao----   8.00m                                                        /dev/sdd1(256)           
  corigin         cache_sanity  Cwi-a-C---   2.00g [POOL] [corigin_corig] 0.00   3.47            100.00   corigin_corig(0)         
  [corigin_corig] cache_sanity  owi-aoC---   2.00g                                                        /dev/sda1(0)             
  [lvol0_pmspare] cache_sanity  ewi-------   8.00m                                                        /dev/sdd1(258)           

[root@host-109 ~]# echo offline > /sys/block/sdd/device/state
[root@host-109 ~]# lvchange -an cache_sanity
[deadlock]


Oct  9 17:59:09 host-109 kernel: sd 4:0:0:1: rejecting I/O to offline device
Oct  9 17:59:09 host-109 kernel: sd 4:0:0:1: rejecting I/O to offline device
Oct  9 17:59:09 host-109 kernel: sd 4:0:0:1: rejecting I/O to offline device
Oct  9 17:59:09 host-109 kernel: device-mapper: cache: 253:3: metadata operation 'dm_cache_commit' failed: error = -5
Oct  9 17:59:09 host-109 kernel: device-mapper: cache: 253:3: aborting current metadata transaction
Oct  9 17:59:09 host-109 kernel: sd 4:0:0:1: rejecting I/O to offline device
Oct  9 17:59:09 host-109 kernel: sd 4:0:0:1: rejecting I/O to offline device
Oct  9 17:59:09 host-109 kernel: device-mapper: cache: 253:3: failed to abort metadata transaction
Oct  9 17:59:09 host-109 kernel: device-mapper: cache: 253:3: switching cache to fail mode
Oct  9 17:59:09 host-109 kernel: device-mapper: cache: 253:3: could not write cache metadata
Oct  9 17:59:09 host-109 kernel: sd 4:0:0:1: rejecting I/O to offline device



Version-Release number of selected component (if applicable):
3.10.0-322.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

Comment 2 Jonathan Earl Brassow 2017-07-27 20:09:23 UTC

Anything we can do for this condition?  abandon the cache?

Comment 4 RHEL Program Management 2020-12-15 07:37:40 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.