Bug 1395298
| Summary: | RHEL 7.3: have rbd multipathd checker set lock_on_read rbd map setting | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> |
| Status: | CLOSED ERRATA | QA Contact: | Lin Li <lilin> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.3 | CC: | agk, bmarzins, ceph-qe-bugs, heinzm, hnallurv, hyelloji, jbrassow, mchristi, mkolaja, msnitzer, mthacker, prajnoha, snagar, yizhan |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | device-mapper-multipath-0.4.9-99.el7_3.1 | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
When a Ceph rbd image is exported through multiple iSCSI targets, the rbd kernel module will grab the exclusive lock when it receives a write request.
Consequence:
If a write request is hung in the rbd module, and the iSCSI initiator and multipath layer decide to fail the request to the application, read requests sent after the failure may not reflect the state of the write.
Fix:
The rbd module will grab the exclusive lock for both reads and writes. This will cause hung writes to be flushed and or failed before executing reads.
Result:
Read requests sent after failed writes will always return the same data.
|
Story Points: | --- |
| Clone Of: | 1380602 | Environment: | |
| Last Closed: | 2017-01-17 18:09:28 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: | 1380602 | ||
| Bug Blocks: | |||
|
Description
Marcel Kolaja
2016-11-15 16:11:51 UTC
Fix backported. Verified the fix on following Builds device-mapper-multipath-0.4.9-99.el7.x86_64 ceph 10.2.3-13.el7cp.x86_64 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-0076.html |