Bug 1086417
| Summary: | multipathd stuck trying to switch to group that does not exist | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | mchristie | |
| Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> | |
| Status: | CLOSED ERRATA | QA Contact: | yanfu,wang <yanwang> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 6.4 | CC: | agk, bmarzins, ccui, dwysocha, heinzm, msnitzer, prajnoha, prockai, rbalakri, yanwang, zkabelac | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | device-mapper-multipath-0.4.9-76.el6 | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: If multipathd failed to add a path to the multipath device table. It would not correctly orphan the path. This would cause multipath to treat the path as if it belonged to a multipath device, when it did not
Consequence: Multipathd could keep trying to switch to a non-existent pathgroup if it failed to add a path to the multipath device.
Fix: multipathd now correctly orphans paths that can't be added to the multipath device table
Result: Multipathd will no longer treat paths that couldn't get added to a multipath device as belonging to the multipath device, and will no longer keep trying to switch to a non-existent pathgroup.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1110007 (view as bug list) | Environment: | ||
| Last Closed: | 2014-10-14 07:43:15 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1110007 | |||
|
Description
mchristie
2014-04-10 20:41:55 UTC
It's pretty straightforward to make multipathd correctly orphan a path, if it fails in adding it. That will stop the repeating failing attempts to switch the path group. However, that doesn't explain the root cause of your issue, which is device-mapper not being able to get the path device. It seems that most likely the cause is that something else was exclusively opening the path device. When this occurs, does /sys/block/<devname>/holders show anything? or does fuser or lsof show the device in use? If it doesn't appear that the device is currently opened exclusively, you could try removing and re-adding it to see if device-mapper is now able to get the device. # multipathd del path <devname> # multipathd add path <devname> Multipath will now correctly orphan paths that don't get added correctly. The easiest way to hit this is to 1. create a multipath device 2. remove a path with # multipathd del path <name> 3. exclusively open the path device, by doing something like mounting a filesystem on it 4. add the path back to multipath with # multipath add path <name> The add will fail. With this fix the device will be orphaned. Without it, the device will still be listed as part of the multipath device, and the checker will keep running on it. 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-2014-1555.html |