We would like to add a patch to RHEL5.3 to support the dual storage controllers in the Intel Modular Server being used with the new scsi_dh framework. This will allow users to setup multipath on the system without loading patches and having to rebuild scsi_dh. The patch has two parts: 1) Change in the scsi-dh framework to accept Intel devices. This is a single line code change to add Intel the Multiflex device name to the supported devices list. This code is in attachment "scsi_dh-patch". 2) User-space tool to give priority of a path depending on the preferred bit of the controller. This tool is based on mpath_prio_alua. For correct failover/failback operations we need the correct priority of the path, this is done by this second tool. This code is in attachment "patch-multipath-tools".
Created attachment 325601 [details] patch-multipath-tools
Created attachment 325602 [details] scsi_dh-patch
Joseph, It is to late for RHEL 5.3. But we need code submitted by 29-Jan-2009 for acceptance into RHEL 5.4. Are the attached patches the latest versions?
John, Yes, attached patches are still the latest and greatest versions, no known issues at this time. Thanks, Joe
Ben, I am going to take the kernel patch in comment #2 and push upstream and then put it in RHEL. I have a bugzilla for the kernel stuff already. You can use this bz for all the multipath tools fun :)
(In reply to comment #1) > Created an attachment (id=325601) [details] > patch-multipath-tools Promise/Intel developers, What is up with this patch? It has IBM copyrights in the header, but then prints out a intel copyright in the print version. Can the default path_priority/pp_alua callout be used instead of adding your own or can the default one be used?
(In reply to comment #6) > Can the default path_priority/pp_alua callout be used instead of adding your > own or can the default one be used? I meant to write modified to support whatever extra you need?
With regard to the question about copyright Promise tells us this is a minor change from the original pp_alua code so we must sustain copyright information in compliance with GPL requirements. With regard to the question about modifying pp_alua this is the response from Promise: We already tested with calling pp_alua, but got a problem which did not get exact priority from device. So it failed to get exact path.
(In reply to comment #8) > > With regard to the question about modifying pp_alua this is the response from > Promise: > We already tested with calling pp_alua, but got a problem which did not get > exact priority from device. So it failed to get exact path. Ok. I am adding some more info since Ben does multipath tools, but in the mail Ilgu sent there was some more detail which would help him know what is going on. Ilgu from Promise also said: We will check and try to find minimize patch size for pp_intel. Intel/Promise guys if you send mail about multipath tools could you make sure to cc Benjamin Marzinski <bmarzins>. I do not do any work with multipath tools. I have no idea what is going on :) He will be able to help you guys with those type of issues.
Note: This BZ corresponds to IT 267306.
what's the status on this BZ? Is it ever going to get moved from NEW to ASSIGNED?
This is on the list of BZs approved for RHEL 5.4.
Patch applied.
~~ 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.
~~ Attention Partners - RHEL 5.4 Snapshot 1 Released! ~~ RHEL 5.4 Snapshot 1 has been released on partners.redhat.com. If you have already reported your test results, you can safely ignore this request. Otherwise, please notice that there should be a fix available now that addresses this particular request. Please test and report back your results here, at your earliest convenience. The RHEL 5.4 exception freeze is quickly approaching. 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. Do not flip the bug status to VERIFIED. Instead, please set your Partner ID in the Verified field above if you have successfully verified the resolution of this issue. Further questions can be directed to your Red Hat Partner Manager or other appropriate customer representative.
Keve - Intel, what's the testing status of this feature? It should be included in the latest snapshots.
Intel, Ping?
Testing is in progress.
Thanks Intel. Please update us with test results or test status as soon as possible.
Hi,all We tested RHEL 5.4 alpa, beta, and snapshot 1 and we found that this version support our device in multipath tools and scsi_dh_alua. we did FO/FB test and we did not find "scsi id issue" which we found in RHEL 5.3 version. So RHEL 5.4 work fine with clearbay. Thanks.
Intel, any update on testing?
Chris, comment #23 reports the results of our testing, we consider this verified and closed from our perspective. Thanks!
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/RHEA-2009-1377.html
closed