RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 463831 - [LTC 6.0 FEAT] 201764:Installer enhancement - FICON Hyper PAV enablement
Summary: [LTC 6.0 FEAT] 201764:Installer enhancement - FICON Hyper PAV enablement
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: s390x
OS: All
high
high
Target Milestone: alpha
: 6.1
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 538808
TreeView+ depends on / blocked
 
Reported: 2008-09-24 20:20 UTC by IBM Bug Proxy
Modified: 2010-10-20 14:18 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-23 17:23:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description IBM Bug Proxy 2008-09-24 20:20:45 UTC 
=Comment: #0=================================================
Emily J. Ratliff <emilyr.com> - 2008-09-24 13:52 EDT
1. Feature Overview:
Feature Id:	[201764]
a. Name of Feature:	Installer enhancement - FICON Hyper PAV enablement
b. Feature Description
DASD related configuration dialogs should not present HyperPAV Alias devices as targets for the
following operations:  formatting  file system creation  mounting    The reason behind this is that
even when a HyperPAV Alias device is set online, no separate block device will be created by the
kernel. Without a block device, none of the operations can be performed.    It should be possible to
configure DASD HyperPAV Alias devices to be automatically activated (set online) during
installation/boot. If an Alias device is not online, it will not be used by the DASD driver.   
Note: with Hyper PAV, no multipath configuration is needed, since everything in handled by the DASD
driver.

2. Feature Details:
Sponsor:	zSeries
Architectures:
s390x

Arch Specificity: Both
Affects Installer: Yes
Delivery Mechanism: Request Red Hat development assistance
Category:	Installation
Request Type:	Installer - Enhancement from Distributor
d. Upstream Acceptance:	No Code Required
Sponsor Priority	1
f. Severity: High
IBM Confidential:	no
Code Contribution:	no
g. Component Version Target:	n/a

3. Business Case
Customers will observe increased and sustained I/O performance improvements exploiting parallel
Access Volume (PAV) support for disk storage access. Supporting HyperPAV will lead to significantly
reduced configuration efforts as opposed to static PAV setups with the system dynamically self
optimizing its I/O configuration.

4. Primary contact at Red Hat: 
John Jarvis
jjarvis

5. Primary contacts at Partner:
Project Management Contact:
Hans-Georg Markgraf, mgrf.com, Boeblingen 49-7031-16-3978

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

IBM Manager:
Thomas Schwarz, t.schwarz.com
Comment 1 Bill Nottingham 2008-09-24 20:52:56 UTC 
Why isn't this using the normal dm-multipath layer?
Comment 2 Gonzalo Muelas Serrano 2008-11-27 14:17:10 UTC 
Because is not needed anymore since now the multipathing for DASD Base+Alias devices is directly implemented in the DASD driver, because with the new DASD driver the aliases devices are not even block devices, which I think is needed for dm-multipath.

Let me know if you want to discuss further DASD driver implementation details with the DASD driver developer and I will be happy to set up a conf. call.

More information about PAV and HyperPAV can be found under:
http://www.ibm.com/developerworks/linux/linux390/development_documentation.html
How to Improve Performance with PAV - SC33-8414-00
Comment 3 Gonzalo Muelas Serrano 2008-11-27 14:18:10 UTC 
Info provided...
Comment 4 John Jarvis 2010-02-05 16:19:30 UTC 
We are out of capacity to complete this for RHEL 6.0 and a Fedora implementation needs to be completed before inclusion in RHEL.  Adding to RHEL 6.1
tracker for consideration for that release.
Comment 5 IBM Bug Proxy 2010-02-19 14:31:22 UTC 
------- Comment From mgrf.com 2010-02-19 09:22 EDT-------
Hello Red Hat,
As per System z work via Fedora 12 this should work in RHEL6.
If limitations get observed in beta tests
->  it can be mentioned in release notes.
Comment 6 John Jarvis 2010-09-23 17:23:27 UTC 
Based on the last comment, closing this as CURRENTRELEASE.  Please open a new bug report if any issues are found in testing the implementation in RHEL 6.0.
Note You need to log in before you can comment on or make changes to this bug.