Description of problem: Update hwtable.c to incorporate default settings for HP active/passive arrays that use dm_hp_sw hardware handler. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Patches for hp hardware handler are now upstream so need to make sure userspace patch is in there. In particular, we changed the kernel name from "hp_sw" to "hp-sw" so that needs to go into the hwtable.c file. Patch was submitted to dm-devel here: https://www.redhat.com/archives/dm-devel/2007-October/msg00008.html
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Just posted rhel4.7 patches to rhkernel for hp-sw hardware handler backport.
New patches posted to rhkernel. Will wait for ack before making userspace change.
Kernel is in, just need to update userspace. Shooting for next week, pending lvm2 bz resolution. Should be fairly straightforward but need to check for the latest and coordinate with the including mpath_prio_hp_sw: https://bugzilla.redhat.com/show_bug.cgi?id=438037
The more important userspace update is now posted to https://bugzilla.redhat.com/show_bug.cgi?id=438037 will work on hwtable.c now but wanted to get that one done first (users can update the hardware table manually if need be).
For the record, here's what I'm testing in the /etc/multipath.conf file: device { vendor "COMPAQ" product "MSA1000 VOLUME" path_grouping_policy group_by_prio hardware_handler "1 hp-sw" path_checker hp_sw features "1 queue_if_no_path" prio_callout "/sbin/mpath_prio_hp_sw /dev/%n" failback immediate }
Oh yeah, I remember now why I was unsure. Upstream is different from RHEL4 and its not clear which was correct for which models. Will try to resolve this now.
For some reason I can't get the updates to hwtable.c to be used / picked up when I run multipath to create the maps. I'm sure I'm using the updated binary. This should be easy, hmmmm....
Created attachment 307225 [details] Update hwtable.c based on latest upstream and other information. I have talked with Ben and I believe we can get a patch that will address this bz in time for Snapshot 3. Just sent a note to Ben with my patch but attaching here for completeness.
This request was previously evaluated by Red Hat Product Management for inclusion in the current Red Hat Enterprise Linux release, but Red Hat was unable to resolve it in time. This request will be reviewed for a future Red Hat Enterprise Linux release.
Patched. Thanks.
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: * device-mapper-multipath now includes hardware table entries to support new HP array products, including product IDs for the XP, EVA, and MSA lines and default settings for HP arrays that use the dm_hp_sw hardware handler.
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/RHBA-2009-1011.html