Bug 631508

Summary: [6.1 FEAT] FICON IPL & device discovery hardening - userspace
Product: Red Hat Enterprise Linux 6 Reporter: IBM Bug Proxy <bugproxy>
Component: s390utilsAssignee: Dan HorĂ¡k <dhorak>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: gmuelas, jjarvis, nobody+PNT0273897, ovasik, sbest
Target Milestone: betaKeywords: FutureFeature
Target Release: 6.1   
Hardware: s390x   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-15 08:48:16 UTC Type: ---
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: 538808, 580566, 633849    

Description IBM Bug Proxy 2010-09-07 19:50:45 UTC
1. Feature Overview:
Feature Id: [66872]
a. Name of Feature: [6.1 FEAT] FICON IPL & device discovery hardening - userspace
b. Feature Description
This feature improves the DASD error recovery procedures used in the early phases of IPL and DASD
device initialization.

With todays code, DASD I/O errors that occur during the IPL and device initialization phase can lead
to limited device availability or even to a complete failure of the system start, although these
errors might have been recoverable. This line item consists of an analysis of the relevant code
paths and, where applicable, an addition or improvement of respective error recovery procedures.

Recoverable error scenarios include:
1. One or more paths to the IPL device report permanent error state (e.g. IFCC, configured off) but
at least one path is usable after restarting the I/O a defined number of retries.
2. One or more paths to the IPL device report temporary error state (e.g. IFCC) which resolves after
a defined number of retries.
3. Paths report permanent error state in the order in which they are tried, but become usable again
immediately afterwords ("link flapping").
4. The I/O operations started by the DASD device driver during device online processing will use the
same error recovery procedures as ???normal??? I/O.
5. In addition to device online processing, the dasd format ioctl (used by the dasdfmt tool) will
also use the standard error recovery procedures.

This is the userspace/tools part. There is a dependent kernel part which is tracked by different
feature request.


2. Feature Details:
Sponsor: LTC zSeries BOE
Architectures:  zSeries - 64 native, 

Arch Specificity: purely arch specific code
Affects Kernel Modules: Field does not exist
Delivery Mechanism: Backport
Category: other
Request Type: Package - Feature from IBM
d. Upstream Acceptance: Field does not exist
Sponsor Priority P1
f. Severity: ship issue
IBM Confidential: No
Code Contribution: IBM code
g. Component Version Target:---

3. Business Case
Improve the RAS capabilities of Linux on System z which is one of the major strengths of Linux in
this platform and why the customers are interested in Linux on System z.

4. Primary contact at Red Hat:
John Jarvis, jjarvis

5. Primary contacts at Partner:
Project Management Contact:
Hans-Georg Markgraf, mgrf.com

Technical contact(s):
Gonzalo Muelas Serrano, gmuelas.com

Comment 2 John Jarvis 2010-09-13 19:49:09 UTC
Is this a new package request?  If so, is the package already in Fedora?  Or will this be part of s390utils?

Comment 3 Gonzalo Muelas Serrano 2010-09-14 09:44:41 UTC
Hello John,
this will be part of s390tools/utils and be provided as a backport to existing
RHEL 6.0 version.
Unfortunately through the mirroring this information got lost. I have updated
the component here directly.

Comment 4 IBM Bug Proxy 2010-10-04 15:30:45 UTC
------- Comment From rsisk.com 2010-10-04 10:36 EDT-------
Code Upstream Status: Accepted

Comment 6 IBM Bug Proxy 2010-12-14 17:32:47 UTC
------- Comment From mgrf.com 2010-12-14 12:30 EDT-------
Just recognize the code for this userspace  feature is already included in
RHEL 6.
It got provided via BZ
59917  -  RIT447083- zipl: handle status during IPL SSCH

Comment 7 John Jarvis 2010-12-14 18:08:43 UTC
Please provie the BZ so I can dupe this request to that one.

Comment 8 Gonzalo Muelas Serrano 2010-12-15 08:47:37 UTC
Sure: Bug 559250 - zipl: handle status during IPL SSCH

Comment 9 Gonzalo Muelas Serrano 2010-12-15 08:48:16 UTC

*** This bug has been marked as a duplicate of bug 559250 ***