Bug 1584228 – multipath daemon is hung in 'D' state with the LSI3408/3508 RAID controller

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1584228 - multipath daemon is hung in 'D' state with the LSI3408/3508 RAID controller

Summary:	multipath daemon is hung in 'D' state with the LSI3408/3508 RAID controller

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	device-mapper-multipath (Show other bugs)
Sub Component:
Version:	7.5
Hardware:	x86_64 Linux

Priority	medium Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Ben Marzinski
QA Contact:	Lin Li
Docs Contact:	Steven J. Levine

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-05-30 10:06 EDT by Dariusz Wojewódzki
Modified:	2018-10-30 07:28 EDT (History)
CC List:	8 users (show)

See Also:
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 07:27:28 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:3236	None	None	None	2018-10-30 07:28 EDT

Groups: None (edit)

Comment 5 Ben Marzinski 2018-06-22 13:08:36 EDT

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 07:27:28 EDT

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

Note You need to log in before you can comment on or make changes to this bug.