Bug 1584228

Summary:	multipath daemon is hung in 'D' state with the LSI3408/3508 RAID controller
Product:	Red Hat Enterprise Linux 7	Reporter:	Dariusz Wojewódzki <dwojewod>
Component:	device-mapper-multipath	Assignee:	Ben Marzinski <bmarzins>
Status:	CLOSED ERRATA	QA Contact:	Lin Li <lilin>
Severity:	medium	Docs Contact:	Steven J. Levine <slevine>
Priority:	medium
Version:	7.5	CC:	agk, bmarzins, dwojewod, heinzm, lilin, msnitzer, prajnoha, rhandlin
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	device-mapper-multipath-0.4.9-121.el7	Doc Type:	Bug Fix
Doc Text:	The `multipathd readsector0` checker now returns the correct result Previously, in some cases the `multipathd` daemon was incorrectly calculating the I/O size to use with the `readsector0` checker, causing it to do a 0 size read. This could cause the `multipathd readsector0` checker to return the wrong result. It is also possible that some SCSI devices do not treat a 0 size read command as valid. With this fix, `multipathd` now uses the correct size for the `readsector0` checker.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-30 11:27:28 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:

Comment 5 Ben Marzinski 2018-06-22 17:08:36 UTC

Multipathd will now request the correct number of blocks for the readsector0 checker in all cases.  I don't know if that's the root cause of this issue, but it should make the checker issue the correct command.  If the controller is still not honoring it, it is more likely a controller issue.

Comment 20 errata-xmlrpc 2018-10-30 11:27:28 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://access.redhat.com/errata/RHBA-2018:3236