Bug 1377532
Summary: | /sbin/multipathd segfaults | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | nikhil kshirsagar <nkshirsa> |
Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> |
Status: | CLOSED ERRATA | QA Contact: | Lin Li <lilin> |
Severity: | high | Docs Contact: | Milan Navratil <mnavrati> |
Priority: | unspecified | ||
Version: | 6.7 | CC: | agk, bmarzins, heinzm, msnitzer, nkshirsa, prajnoha, rbalakri, yizhan, zkabelac |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | device-mapper-multipath-0.4.9-94.el6 | Doc Type: | Release Note |
Doc Text: |
The "disable_changed_wwids" `multipath.conf` option is now available in multipath to avoid data corruption
The multipath tool now has the "disable_changed_wwids" `multipath.conf` option. If "disable_changed_wwids" is set to "yes", the *multipathd* service monitors path devices, and if their World Wide Identifier (WWID) changes, *multipathd* disables access to the path devices until the WWID changes back.
If a Logical Unit Number (LUN) is remapped while a multipath device exists on top of it, it is possible in some cases for I/O to be written to an incorrect LUN, which leads to corruption. Writing to an incorrect LUN can be detected by *multipathd* that registers a change of the LUN WWID, and disables access to the device.
Note that due to the gap between when the LUN is remapped, and when *multipathd* is notified that the device has changed, there is still a risk of corruption in some cases, and remapping in-use LUNs is still not supported.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-03-21 10:52:57 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
nikhil kshirsagar
2016-09-20 03:44:17 UTC
I've added a new multipath.conf option, "disable_changed_wwids". With this set, whenever it gets a uevent for a path device, multipathd will verify that the wwid hasn't changed. If it has, multipathd will disable the path until the wwid changes back to the value of the multipath device that it is a part of. 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. https://rhn.redhat.com/errata/RHBA-2017-0697.html |