[17.04 FEAT] DASD channel-path aware error recovery
Bug #1644537 reported by
bugproxy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Fix Released
|
Medium
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Medium
|
Canonical Kernel Team |
Bug Description
Enhance the DASD driver to log path situations as an error and try to exclude paths from further I/Os without risking an out-of-path situation to enable users to reset this state when the cause has been resolved.
Example:
If a DASD is connected via multiple paths and one of these paths does not work correctly (e.g. constant IFCCs, channel checks, or because HPF has stopped working on this path),
Improve RAS especially during setup using DASDs. Resolve customer request, avoid field reported problems
tags: | added: architecture-s39064 bugnameltc-149077 severity-high targetmilestone-inin1704 |
Changed in ubuntu: | |
assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
affects: | ubuntu → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
milestone: | none → ubuntu-17.03 |
assignee: | Skipper Bug Screeners (skipper-screen-team) → Canonical Kernel (canonical-kernel) |
Changed in ubuntu-z-systems: | |
status: | New → Confirmed |
Changed in ubuntu-z-systems: | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in ubuntu-z-systems: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
Is a target linux kernel version known for this feature? Links to public git commit ids? I am failing to identify this in v4.9-rc6- 157-g16ae16c