Hide Forgot
Description of problem: Neither manpage nor "/usr/share/doc/device-mapper-multipath-0.4.9" provide any info about "hwtable_regex_match" feature introduced by Bug #744756. Version-Release number of selected component (if applicable): device-mapper-multipath-0.4.9-48.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. No document found for "hwtable_regex_match" Actual results: No document to explain how "hwtable_regex_match" work. Expected results: https://bugzilla.redhat.com/show_bug.cgi?id=744756#c15 could be good document for this parameter. quote: "hwtable_regex_match". Setting it to "yes" will cause the user devices configs to be regex matched with the builtin configs to determine if they should modify an existing config or create a new one. It defaults to "off". Additional info:
Documentation added
Ben, Where you store the documents? I got nothing in /usr/share/docs ==== [fge@RHEL6-Stable ~]$ grep hwtable /usr/share/doc/device-mapper-multipath-0.4.9/* [fge@RHEL6-Stable ~]$ rpm -q device-mapper-multipath device-mapper-multipath-0.4.9-54.el6.x86_64 ==== Thanks.
The multipath.conf man page.
These is a typo in it: ==== If set to yes , user device configs will be regular expression matched against the builtin configs to determine if they should modify an existing config or create a new one. If set to no , user device configs will be string matched against the builtin configs to determine if they shoudl modify an existing # ^^^^^^ config or create a new one. Default is no ===== And meanwhile, can you also add description to "multipath.conf.annotated" and "multipath.conf.defaults". Thanks
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: To modify a built-in device configuration in dm-multipath, the user configuration had to match the vendor and product strings exactly Consequence: This caused problems, since the vendor and product strings are regular expressions. Change: A new default configuration option was added, "hwtable_regex_match". If this is set to "yes", instead of using string matching, the vendor and product of the user configuration is matched against the built-in configurations using the same regex matching as the devices use. The option defaults to "no" Result: Users can now simply set hwtable_regex_match and copy the vendor and product strings from their devices when modifying the built-in device configurations, and they will automatically modify the correct configuration.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,7 +1 @@ -Cause: To modify a built-in device configuration in dm-multipath, the user configuration had to match the vendor and product strings exactly +No documentation needed- -Consequence: This caused problems, since the vendor and product strings are regular expressions. - -Change: A new default configuration option was added, "hwtable_regex_match". If this is set to "yes", instead of using string matching, the vendor and product of the user configuration is matched against the built-in configurations using the same regex matching as the devices use. The option defaults to "no" - -Result: Users can now simply set hwtable_regex_match and copy the vendor and product strings from their devices when modifying the built-in device configurations, and they will automatically modify the correct configuration.
Ben, Any reply for comment #6? You want it fixed in RHEL 6.4?
I was planning on putting this in if was going to respin the package for 6.3. But it doesn't look like I'm going to do so. So, I'll fix this for 6.4. Unless I do end up doing a respin
I will verify this bug and clone it to RHEL 6.4 for future update.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0946.html