IPR driver causes multipath to fail paths/stuck IO on Medium Errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Triaged
|
High
|
Canonical Kernel Team | ||
Xenial |
Fix Released
|
High
|
Unassigned | ||
Zesty |
Fix Released
|
High
|
Unassigned |
Bug Description
SRU Justification:
Impact: stuck I/O to multipath disks with medium errors (on IPR controllers)
Fix: upstream commit for IPR driver to allow SCSI layer to handle the error
Testcase: perform I/O to a failing disk which is multipathed (on IPR
the I/O gets stuck).
the commit message describes a test-case w/ sg_dd.
---Problem Description---
IPR driver causes multipath to fail paths/stuck IO on Medium Errors
This problem is resolved with this upstream accepted patch, scheduled for 4.11.
The detailed problem description and resolution are described in the commit message.
> scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION
> https:/
Please apply to 17.04 (target 16.04.3 HWE kernel) and 16.04 (GA kernel).
Patch already applied to 17.10.
The business justification for the SRU is:
Clients with a dual-controller multipathed IPR configuration that eventually runs into failing disk/sectors, will experience an I/O hang once the drive reports a Medium Error, which can hang an application or even the root filesystem (whatever is doing I/O to the failing drive), potentially hanging the system.
Thanks.
---Additional Hardware Info---
Dual (IPR) controller setup, multipath enabled
---Steps to Reproduce---
1) Use a disk with bad sectors (or force such condition, via internal/special tools)
2) Multipath that disk
3) Run IO to the multipath device on the bad sectors
4) Both paths will be failed, and IO is stuck due to queue_if_no_path (enabled by default for IPR)
The detailed problem description and resolution are described in the commit message.
CVE References
tags: | added: architecture-ppc64le bugnameltc-153445 severity-critical targetmilestone-inin16043 |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
affects: | ubuntu → linux (Ubuntu) |
tags: | added: kernel-da-key |
Changed in linux (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → Canonical Kernel Team (canonical-kernel-team) |
importance: | Undecided → High |
status: | New → Triaged |
Changed in linux (Ubuntu Xenial): | |
status: | New → Triaged |
Changed in linux (Ubuntu Zesty): | |
status: | New → Triaged |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → High |
Changed in linux (Ubuntu Zesty): | |
importance: | Undecided → High |
tags: |
added: severity-high removed: severity-critical |
Changed in linux (Ubuntu Zesty): | |
status: | Triaged → Fix Committed |
Changed in linux (Ubuntu Xenial): | |
status: | Triaged → Fix Committed |
------- Comment From <email address hidden> 2017-08-14 13:12 EDT-------
This one hasn't been touched in months... We need to get this fix into a 16.04 SRU...