Bug 517951
Summary: | [FOCUS] DM multipath kernel driver version too old | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | IBM Bug Proxy <bugproxy> | ||||
Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> | ||||
Status: | CLOSED ERRATA | QA Contact: | Gris Ge <fge> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5.4 | CC: | agk, bhu, bmarzins, bmr, christophe.varoqui, coughlan, dwysocha, egoggin, fge, heinzm, iannis, jkacur, junichi.nomura, kueda, lgoncalv, lmb, mbroz, prockai, rmusil, tranlan, williams | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
The kernel driver of device-mapper multipath could appear to be old and SAN boot could fail, because the version testing of the driver was not correct. Version testing is now implemented correctly.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-01-13 23:01:41 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: | |||||||
Attachments: |
|
Description
IBM Bug Proxy
2009-08-18 06:30:33 UTC
------- Comment From sekharan.com 2009-08-20 14:56 EDT------- Looks like the following patch need to be ported. http://git.kernel.org/?p=linux/storage/multipath-tools/.git;a=commit;h=d0d111d16e8af297111dc05ec84ddf06e9a109f1 Created attachment 358268 [details] Ported+Tested patch. ------- Comment on attachment From jvrao.com 2009-08-21 14:09 EDT------- I have ported and tested the community patch as mentioned in the comment#7. The port was onto multipath-tools-0.4.7.rhel5.13 source (device-mapper-multipath-0.4.7-23.el5.src.rpm) Could someone please verify whether jvrao's patch was applied to the multipath-tools and if we can close this bug? thanks ------- Comment From jvrao.com 2009-10-13 02:13 EDT------- (In reply to comment #10) > Could someone please verify whether jvrao's patch was applied to the > multipath-tools and if we can close this bug? > > thanks > Hi Any update on this? Is this into RHEL 5.4? no update yet Reassigning to Lana (documentation) so we can put a MRG 1.2 Release Note out for this (no way to get it into RHEL5.4 for MRG release). Lana, we need to make sure that we have a Release Note documenting the bogus warning issued by the device-mapper-multipath tool for RHEL5 when booting the MRG v2 kernel. ------- Comment From jvrao.com 2009-10-15 17:17 EDT------- (In reply to comment #13) > Reassigning to Lana (documentation) so we can put a MRG 1.2 Release Note out > for this (no way to get it into RHEL5.4 for MRG release). > > Lana, we need to make sure that we have a Release Note documenting the bogus > warning issued by the device-mapper-multipath tool for RHEL5 when booting the > MRG v2 kernel. > I think it is more than a documentation issue. Warning is bogus alright but it fails the command. This goes to an extent, where one can't SAN boot the MRG 1.2 on RHEL5.4 based system. The workaround is to get the SRPM, apply the patch, replace /sbin/multipath and /sbin/multipath.static, install MRG 1.2 RPMS and then proceed. Thanks, JV I did not realize that the command failed, just thought it was a warning. Reassigning... Reassigned to RHEL (per tcoughlin) Do we have any pending update on this? ping Patch applied. Reproduced this bug with kernel 2.6.33.7-rt29.45.el5rt, multipath 0.4.7-34.el5 Got the same error as customer. device-mapper-multipath-0.4.7-39.el5 fixed this problem. 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: The kernel driver of device-mapper multipath could appear to be old and SAN boot could fail, because the version testing of the driver was not correct. Version testing is now implemented correctly. 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-2011-0074.html |