Bug 700927

Summary:	dm_task_run failed, errno = 6, No such device or address
Product:	Red Hat Enterprise Linux 5	Reporter:	Corey Marthaler <cmarthal>
Component:	lvm2	Assignee:	Jonathan Earl Brassow <jbrassow>
Status:	CLOSED WONTFIX	QA Contact:	Corey Marthaler <cmarthal>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.6	CC:	agk, dwysocha, heinzm, jbrassow, mbroz, prajnoha, prockai, thornber, zkabelac
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	728565 (view as bug list)		Environment:
Last Closed:	2012-04-20 13:45:01 UTC	Type:	---
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:
Bug Blocks:	728565, 807971

Description Corey Marthaler 2011-04-29 19:52:57 UTC

Description of problem:
I'm seeing this error quite a bit while doing mirror failure testing.

[root@taft-01 ~]# grep dm_task_run /var/log/messages | grep failed | grep 6
Apr 28 15:26:31 taft-01 lvm[7855]: dm_task_run failed, errno = 6, No such device or address
Apr 28 18:02:39 taft-01 lvm[7300]: dm_task_run failed, errno = 6, No such device or address
Apr 28 18:02:56 taft-01 lvm[7300]: dm_task_run failed, errno = 6, No such device or address
Apr 29 12:07:33 taft-01 lvm[7300]: dm_task_run failed, errno = 6, No such device or address
Apr 29 12:26:21 taft-01 lvm[7300]: dm_task_run failed, errno = 6, No such device or address
Apr 29 12:27:13 taft-01 lvm[7300]: dm_task_run failed, errno = 6, No such device or address
Apr 29 12:54:41 taft-01 lvm[7300]: dm_task_run failed, errno = 6, No such device or address
Apr 29 12:55:32 taft-01 lvm[7300]: dm_task_run failed, errno = 6, No such device or address
Apr 29 12:56:23 taft-01 lvm[7300]: dm_task_run failed, errno = 6, No such device or address
Apr 29 13:19:21 taft-01 lvm[7300]: dm_task_run failed, errno = 6, No such device or address
Apr 29 13:38:23 taft-01 lvm[7300]: dm_task_run failed, errno = 6, No such device or address


Apr 28 15:26:31 taft-01 lvm[7855]: 2 missing and now unallocated Physical Volumes removed from VG.
Apr 28 15:26:31 taft-01 lvm[7855]: Repair of mirrored LV helter_skelter/syncd_pri_leg_pri_log_2legs_2logs_1 finished successfully.
Apr 28 15:26:31 taft-01 lvm[7855]: Primary mirror device 253:5 has failed (D).
Apr 28 15:26:31 taft-01 lvm[7855]: Device failure in helter_skelter-syncd_pri_leg_pri_log_2legs_2logs_1.
Apr 28 15:26:31 taft-01 lvm[7855]: dm_task_run failed, errno = 6, No such device or address
Apr 28 15:26:31 taft-01 lvm[7855]: helter_skelter-syncd_pri_leg_pri_log_2legs_2logs_1_mlog disappeared, detaching
Apr 28 15:26:31 taft-01 lvm[7855]: No longer monitoring mirror device helter_skelter-syncd_pri_leg_pri_log_2legs_2logs_1_mlog for events.
Apr 28 15:26:32 taft-01 lvm[7855]: Repair of mirrored LV helter_skelter/syncd_pri_leg_pri_log_2legs_2logs_1 finished successfully.



Apr 29 13:38:23 taft-01 lvm[7300]: 2 missing and now unallocated Physical Volumes removed from VG.
Apr 29 13:38:23 taft-01 lvm[7300]: Repair of mirrored LV helter_skelter/syncd_pri_leg_pri_log_2legs_2logs_1 finished successfully.
Apr 29 13:38:23 taft-01 lvm[7300]: Primary mirror device 253:5 has failed (D).
Apr 29 13:38:23 taft-01 lvm[7300]: Device failure in helter_skelter-syncd_pri_leg_pri_log_2legs_2logs_1.
Apr 29 13:38:23 taft-01 lvm[7300]: dm_task_run failed, errno = 6, No such device or address
Apr 29 13:38:23 taft-01 lvm[7300]: helter_skelter-syncd_pri_leg_pri_log_2legs_2logs_1_mlog disappeared, detaching
Apr 29 13:38:23 taft-01 lvm[7300]: No longer monitoring mirror device helter_skelter-syncd_pri_leg_pri_log_2legs_2logs_1_mlog for events.
Apr 29 13:38:23 taft-01 lvm[7300]: Repair of mirrored LV helter_skelter/syncd_pri_leg_pri_log_2legs_2logs_1 finished successfully.


Version-Release number of selected component (if applicable):
2.6.18-256.el5

lvm2-2.02.84-3.el5    BUILT: Wed Apr 27 03:42:24 CDT 2011
lvm2-cluster-2.02.84-3.el5    BUILT: Wed Apr 27 03:42:43 CDT 2011
device-mapper-1.02.63-2.el5    BUILT: Fri Mar  4 10:23:17 CST 2011
device-mapper-event-1.02.63-2.el5    BUILT: Fri Mar  4 10:23:17 CST 2011
cmirror-1.1.39-10.el5    BUILT: Wed Sep  8 16:32:05 CDT 2010
kmod-cmirror-0.1.22-3.el5    BUILT: Tue Dec 22 13:39:47 CST 2009


How reproducible:
Often

Comment 1 Milan Broz 2011-06-06 11:49:26 UTC

Is it still issue with the latest rpms?

Comment 2 Corey Marthaler 2011-06-06 21:03:13 UTC

Yes.

Jun  6 15:43:59 taft-01 lvm[6413]: helter_skelter-nonsyncd_secondary_3legs_1 is now in-sync.
Jun  6 15:43:59 taft-01 lvm[6413]: helter_skelter-nonsyncd_secondary_3legs_1_mimagetmp_3 is now in-sync.
Jun  6 15:43:59 taft-01 lvm[6413]: dm_task_run failed, errno = 6, No such device or address
Jun  6 15:43:59 taft-01 lvm[6413]: helter_skelter-nonsyncd_secondary_3legs_1_mimagetmp_3 disappeared, detaching
Jun  6 15:43:59 taft-01 lvm[6413]: No longer monitoring mirror device helter_skelter-nonsyncd_secondary_3legs_1_mimagetmp_3 for events.
Jun  6 15:43:59 taft-01 lvm[6413]: helter_skelter-nonsyncd_secondary_3legs_1 is now in-sync.

Version:
2.6.18-261.el5

lvm2-2.02.84-4.el5    BUILT: Thu Jun  2 05:04:32 CDT 2011
lvm2-cluster-2.02.84-3.el5    BUILT: Wed Apr 27 03:42:43 CDT 2011
device-mapper-1.02.63-3.el5    BUILT: Thu May 19 08:09:22 CDT 2011
device-mapper-event-1.02.63-3.el5    BUILT: Thu May 19 08:09:22 CDT 2011
cmirror-1.1.39-10.el5    BUILT: Wed Sep  8 16:32:05 CDT 2010
kmod-cmirror-0.1.22-3.el5    BUILT: Tue Dec 22 13:39:47 CST 2009

Comment 8 RHEL Program Management 2012-04-02 10:22:37 UTC

This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 10 RHEL Program Management 2012-04-20 13:45:01 UTC

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.