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.

Bug 1401769

Summary:	"chk_st dev_st" stays "ready running" after offline the device
Product:	Red Hat Enterprise Linux 6	Reporter:	Zhang Yi <yizhan>
Component:	device-mapper-multipath	Assignee:	Ben Marzinski <bmarzins>
Status:	CLOSED ERRATA	QA Contact:	Lin Li <lilin>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.9	CC:	agk, bmarzins, contentsmajestic, heinzm, msnitzer, prajnoha, rbalakri, thisisthomasmore, zkabelac
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	device-mapper-multipath-0.4.9-98.el6	Doc Type:	Bug Fix
Doc Text:	Cause: When a path device is orphaned (no a member of a multipath device), he device state and checker state displayed with the "show paths" command is the state of the device before it was orphaned. Consequence: the show paths command shows out of date information on devices that is no longer checking. Fix: the "show paths" command now displays "undef" as the checker state and "unknown" as the device state of orphaned paths. Result: Users no longer get potentially confusing stale data for devices that aren't being checked.	Story Points:	---
Clone Of:
Clones:	1402092 (view as bug list)		Environment:
Last Closed:	2017-03-21 10:53:18 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:
Bug Blocks:	1402092

Comment 3 Ben Marzinski 2016-12-06 22:47:34 UTC

Multipathd now prints "undef" as the checker state and "unknown" as the device state for orphaned paths.

Comment 5 Lin Li 2016-12-14 07:12:51 UTC

Reproduced on device-mapper-multipath-0.4.9-97.el6
1.# rpm -qa | grep multipath 
device-mapper-multipath-0.4.9-97.el6.x86_64
device-mapper-multipath-libs-0.4.9-97.el6.x86_64
2.# modprobe scsi_debug vpd_use_hostno=0 add_host=2 dev_size_mb=1024
3.# lsblk
NAME                                MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sdb                                   8:16   0 465.8G  0 disk  
sdc                                   8:32   0    50G  0 disk  
└─mpathb (dm-0)                     253:0    0    50G  0 mpath 
  ├─mpathbp1 (dm-1)                 253:1    0   500M  0 part  /boot
  └─mpathbp2 (dm-2)                 253:2    0  49.5G  0 part  
    ├─vg_storageqe73-lv_root (dm-3) 253:3    0  41.8G  0 lvm   /
    └─vg_storageqe73-lv_swap (dm-4) 253:4    0   7.7G  0 lvm   [SWAP]
sde                                   8:64   0    10G  0 disk  
sdd                                   8:48   0    10G  0 disk  
sda                                   8:0    0    50G  0 disk  
└─mpathb (dm-0)                     253:0    0    50G  0 mpath 
  ├─mpathbp1 (dm-1)                 253:1    0   500M  0 part  /boot
  └─mpathbp2 (dm-2)                 253:2    0  49.5G  0 part  
    ├─vg_storageqe73-lv_root (dm-3) 253:3    0  41.8G  0 lvm   /
    └─vg_storageqe73-lv_swap (dm-4) 253:4    0   7.7G  0 lvm   [SWAP]
sdf                                   8:80   0     1G  0 disk  
sdg                                   8:96   0     1G  0 disk

4.# echo "offline" > /sys/block/sdc/device/state
5.# multipath -ll
mpathb (36001405b2273e3a63a94543ad1712953) dm-0 LIO-ORG,IBLOCK
size=50G features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=0 status=enabled
| `- 3:0:0:0  sdc 8:32 failed faulty running
`-+- policy='round-robin 0' prio=1 status=active
  `- 2:0:0:0  sda 8:0  active ready  running
6.# multipath -r
Dec 14 04:43:15 | A dynamic linking error occurred: (/lib64/multipath/libprio.so: cannot open shared object file: No such file or directory)
reload: mpathb (36001405b2273e3a63a94543ad1712953) undef LIO-ORG,IBLOCK
size=50G features='0' hwhandler='0' wp=undef
`-+- policy='round-robin 0' prio=1 status=undef
  `- 2:0:0:0 sda 8:0  active ready  running
7.# multipathd show paths
hcil    dev dev_t pri dm_st  chk_st dev_st  next_check     
3:0:0:0 sdc 8:32  1   undef  faulty offline orphan         <------------
2:0:0:0 sda 8:0   1   active ready  running X......... 3/20


Verified on device-mapper-multipath-0.4.9-99.el6
1. # rpm -qa | grep multipath
device-mapper-multipath-debuginfo-0.4.9-99.el6.x86_64
device-mapper-multipath-libs-0.4.9-99.el6.x86_64
device-mapper-multipath-0.4.9-99.el6.x86_64
2.# modprobe scsi_debug vpd_use_hostno=0 add_host=2 dev_size_mb=1024
3.# lsblk
NAME                                MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
sda                                   8:0    0   50G  0 disk  
└─mpatha (dm-0)                     253:0    0   50G  0 mpath 
  ├─mpathap1 (dm-1)                 253:1    0  500M  0 part  /boot
  └─mpathap2 (dm-2)                 253:2    0 49.5G  0 part  
    ├─vg_storageqe84-lv_root (dm-3) 253:3    0 41.7G  0 lvm   /
    └─vg_storageqe84-lv_swap (dm-4) 253:4    0  7.9G  0 lvm   [SWAP]
sdb                                   8:16   0   50G  0 disk  
└─mpatha (dm-0)                     253:0    0   50G  0 mpath 
  ├─mpathap1 (dm-1)                 253:1    0  500M  0 part  /boot
  └─mpathap2 (dm-2)                 253:2    0 49.5G  0 part  
    ├─vg_storageqe84-lv_root (dm-3) 253:3    0 41.7G  0 lvm   /
    └─vg_storageqe84-lv_swap (dm-4) 253:4    0  7.9G  0 lvm   [SWAP]
sr0                                  11:0    1 1024M  0 rom   
sdc                                   8:32   0    1G  0 disk  
sdd                                   8:48   0    1G  0 disk  
4.# echo "offline" > /sys/block/sdb/device/state
5.# multipath -ll
mpatha (360fff19abdd9552f8a36e5355226ba27) dm-0 EQLOGIC,100E-00
size=50G features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| `- 0:0:0:0 sda 8:0  active ready running
`-+- policy='round-robin 0' prio=0 status=enabled
  `- 1:0:0:0 sdb 8:16 failed faulty running
6.# multipath -r
reload: mpatha (360fff19abdd9552f8a36e5355226ba27) undef EQLOGIC,100E-00
size=50G features='0' hwhandler='0' wp=undef
`-+- policy='round-robin 0' prio=1 status=undef
  `- 0:0:0:0 sda 8:0  active ready running
7.# multipathd show paths
hcil    dev dev_t pri dm_st  chk_st dev_st  next_check      
0:0:0:0 sda 8:0   1   active ready  running XXXXXXX... 14/20
1:0:0:0 sdb 8:16  1   undef  undef  unknown orphan       <---------------
Multipathd now prints "undef" as the checker state and "unknown" as the device state for orphaned paths.



Test result:Multipathd now prints "undef" as the checker state and "unknown" as the device state for orphaned paths.

Comment 7 errata-xmlrpc 2017-03-21 10:53:18 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0697.html

Comment 8 ThomasMore 2020-06-19 10:40:15 UTC

Understanding the inquiry is the initial step, however, it is Similarly significant that you utilize the accessible time. Understudies regularly think little of the measure of work required to compose a decent exposition, which brings about two things: (1) late evenings at the library, and (2) a baffling evaluation. On the off chance that you need to accomplish a decent imprint, you should begin arranging your paper the second you get the article question. The accompanying table might be a valuable guide.
By: https://www.writemyessays.org.uk/

Comment 9 Content Majestic 2020-11-28 06:20:10 UTC

Even though your author may perhaps not have the capability to respond to you immediately, our great service crew is online 24/7 throughout every season.  Some of the agents will listen to out you and give an effective solution or indicate actionable information.  They are the primary place to see if you might have trouble placing a purchase or wish to know your order standing.  Want to go over your own present order?  Searching for a thing that's not listed on the website and/or in the purchase shape?  Curious about the operating process?  Do not be afraid to become connected utilizing a telephone or live chat.
By: https://www.contentmajestic.com/