Bug 487443
| Summary: | [RHEL4 U5] dm-multipath: multipath command fails when a path is added to a map with failed path. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Ben Marzinski <bmarzins> |
| Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> |
| Status: | CLOSED ERRATA | QA Contact: | Gris Ge <fge> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.8 | CC: | agk, bdonahue, bmarzins, bmr, christophe.varoqui, coughlan, cward, dejohnso, dwysocha, egoggin, fge, heinzm, iannis, i-kitayama, jnomura, junichi.nomura, jwest, kueda, lmb, mbroz, prockai, syeghiay, tao, tom, tranlan |
| Target Milestone: | rc | Keywords: | OtherQA |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
The kernel will not allow multipath to reload a table with a failed path in it.
Consequence:
Multipath is unable to reconfigure a multipath device while multipathd is running. This includes being unable to add new paths to the device.
Workaround:
First stop multipathd (service multipathd stop). Then run multipath to reconfigure the device. Finally restart multipathd.
Result:
running the multipath command while multipathd is stopped will cause multipath to remove the failed path from the device table when it reconfigures. This will allow the new path to be added. However, when the failed path comes back online, it will no longer be part of the multipath device. Multipath must be manually run again to reintegrate this device. However, if there are no failed paths, it will not be necessary to stop multipathd before doing this.
|
Story Points: | --- |
| Clone Of: | 194411 | Environment: | |
| Last Closed: | 2011-02-16 14:23:54 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: | 194411 | ||
| Bug Blocks: | |||
|
Comment 1
Issue Tracker
2009-11-12 08:26:32 UTC
Technical Note added. 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: The kernel will not allow multipath to reload a table with a failed path in it. Consequence: Multipath is unable to reconfigure a multipath device while multipathd is running. This includes being unable to add new paths to the device. Workaround: First stop multipathd (service multipathd stop). Then run multipath to reconfigure the device. Finally restart multipathd. Result: running the multipath command while multipathd is stopped will cause multipath to remove the failed path from the device table when it reconfigures. This will allow the new path to be added. However, when the failed path comes back online, it will no longer be part of the multipath device. Multipath must be manually run again to reintegrate this device. However, if there are no failed paths, it will not be necessary to stop multipathd before doing this. Technical note added, change this bug into verify mode. Release team will handle the documentation part for errata 10217. 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-2011-0243.html Hi, I can not find this technical note anywhere.. I looked in the release notes document and in the latest multipath document on doc.redhat.com. There is not a technical notes document in 4.x as there is for RHEL5.. so can I find out where this was documented for the customer. Thanks in advance. |