Bug 461288
Summary: | [EMC 5.4 feat] Require kernel support to issue Control I/O to CKD dasd on EMC Symmetrix arrays | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Nigel Hislop <hislop_nigel> | ||||
Component: | kernel | Assignee: | Hans-Joachim Picht <hpicht> | ||||
Status: | CLOSED ERRATA | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 5.4 | CC: | andriusb, berthiaume_wayne, chellwig, coughlan, cward, dzickus, hislop_nigel, jjarvis, peterm, rlerch, rwheeler, swells, syeghiay | ||||
Target Milestone: | beta | Keywords: | FutureFeature, OtherQA | ||||
Target Release: | 5.4 | ||||||
Hardware: | s390x | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Enhancement | |||||
Doc Text: |
Support has been added to the kernel to issue EMC Symmetrix Control I/O. This update provides the ability to manage EMC Symmetrix storage arrays with Red Hat Enterprise Linux on the IBM System z platform.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-09-02 08:22:26 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: | 459808, 483701, 483784, 485920 | ||||||
Attachments: |
|
Description
Nigel Hislop
2008-09-05 16:31:35 UTC
Who at IBM is driving this patch as well? Primarily: Martin Schwidefsky <schwidefsky.com> Secondary: Stefan Weinhuber <WEIN.com> Holger Smolinski <smolinski.com> The patch was developed on kernel version 2.6.26.2 stable Great, thanks Nigel. Please post a link to the upstream commit when that occurs. RHEL 5.3 is possibly a little aggressive for this patch. Any thoughts regarding pushing this out to a later release? I don't have tentative dates for 5.4 and 6 though. Are any available? Nigel, can you summarize what the impact is on not having this patch out? What functionality breaks for our 390 customers with a Symm? If it is more critical, it can have a more aggressive schedule. Also, it helps the process here a lot if you can get the IBM people to bless the patch for the mainstream kernel. Without this patch, we are not able to discover CKD devices on s390x platforms. For mainframe customers who have only have CKD devices, this means that they cannot manage their Symmetrix arrays with EMC's storage management products on RHEL systems. As the kernel for RHEL 5.3 is already frozen, we need to push this out. Is there any awareness of tentative releases dates for RHEL 5.4 and RHEL 6 ? Nigel, please contact Wayne or I directly - I can't post release dates in a public bugzilla. Updating version to RHEL 5.4 Updating PM score. Hans, Is this something you could handle, if-and-when we get a patch? Tom *** Bug 483154 has been marked as a duplicate of this bug. *** Nigel - please post a link to the upstream patch if you could... thanks! Moving across some updates from 483154 Refer to the 2.6.28 git upstream patch at: http://preview.tinyurl.com/awncad or http://git390.osdl.marist.edu/cgi-bin/gitweb.cgi?p=linux-2.6.git;a=commit;h=ab1d848fd6a9151b02c6cbf4bddce6e24707b094 Attaching RHEL 5.2 patch slightly modified from upstream patch (ckd device structure change) Created attachment 333738 [details]
RHEL 5.2 patch for EMC Symmetrix CKD ioctl
Patch built and tested on RHEL 5.2 kernel
Hans, any progress on testing this patch? Do you need help getting this done? Regards, Ric Ric, I can't test this because I don't have access to the required EMC hardware. Most likely someone from EMC has to test this. Regards, --Hans Hi Hans, I assume that Nigel who authored the patch can verify and test. Tom, were you looking for a reviewer? I can test if an installable version of the RHEL 5.4 kernel is available Hans - any updates here? Are you waiting for feedback from EMC? in kernel-2.6.18-152.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 Please do NOT transition this bugzilla state to VERIFIED until our QE team has sent specific instructions indicating when to do so. However feel free to provide a comment indicating that this fix has been verified. Should there be 152 folder? I'm only seeing these 149.el5/ 19-May-2009 15:56 - 150.el5/ 21-May-2009 11:51 - 151.el5/ 28-May-2009 14:03 - Nigel - give it till the end of the day - doesn't look like Don has uploaded that version yet to his people page. Keep an eye on it! :-) Sorry, should be there now. Testing with 152.el5 looks good and I believe the fix is correct. Thank you. RHEL release information is still showing up as 5.3 though. [root@LN165014 nbh]# cat /etc/*releas* cat: /etc/lsb-release.d: Is a directory Red Hat Enterprise Linux Server release 5.3 (Tikanga) [root@LN165014 nbh]# uname -a Linux LN165014 2.6.18-152.el5 #1 SMP Wed Jun 3 18:57:17 EDT 2009 s390x s390x s390x GNU/Linux ~~ Attention Partners RHEL 5.4 Partner Alpha Released! ~~ RHEL 5.4 Partner Alpha has been released on partners.redhat.com. There should be a fix present that addresses this particular request. Please test and report back your results here, at your earliest convenience. Our Public Beta release is just around the corner! If you encounter any issues, please set the bug back to the ASSIGNED state and describe the issues you encountered. If you have verified the request functions as expected, please set your Partner ID in the Partner field above to indicate successful test results. Do not flip the bug status to VERIFIED. Further questions can be directed to your Red Hat Partner Manager. Thanks! ~~ Attention - RHEL 5.4 Beta Released! ~~ RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner! If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity. Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value. Questions can be posted to this bug or your customer or partner representative. Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: This patch creates ioctl 240 that will allow EMC products to issue EMC Symmetrix Control I/O, ultimately allowing customers to manage their Symmetrix arrays with EMC's storage management products on Red Hat Enterprise Linux for System z instances. Confirmed that this fix/patch works Red Hat Enterprise Linux Server release 5.4 Beta (Tikanga) 2.6.18-155.el5 #1 SMP Fri Jun 19 17:08:22 EDT 2009 s390x s390x s390x GNU/Linux Thank you. Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -This patch creates ioctl 240 that will allow EMC products to issue EMC Symmetrix Control I/O, ultimately allowing customers to manage their Symmetrix arrays with EMC's storage management products on Red Hat Enterprise Linux for System z instances.+Support has been added to the kernel to issue EMC Symmetrix Control I/O. This update provides the ability to manage EMC Symmetrix storage arrays with Red Hat Enterprise Linux on the IBM System z platform. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-1243.html |