Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1348372 - Add multipathd RBD path checker
Add multipathd RBD path checker
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: device-mapper-multipath (Show other bugs)
7.3
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Ben Marzinski
ceph-qe-bugs
Steven J. Levine
:
Depends On:
Blocks: 1298558 1379890
  Show dependency treegraph
 
Reported: 2016-06-20 22:05 EDT by Mike Christie
Modified: 2017-05-22 04:29 EDT (History)
14 users (show)

See Also:
Fixed In Version: device-mapper-multipath-0.4.9-98.el7
Doc Type: Enhancement
Doc Text:
Multipath now includes support for Ceph RADOS block devices. RDB devices need special `uid` handling and their own checker function with the ability to repair devices. With this release, it is now possible to run multipath on top of RADOS block devices. Note, however, that the multipath RBD support should be used only when an RBD image with the `exclusive-lock` feature enabled is being shared between multiple clients.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-04 04:19:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2536 normal SHIPPED_LIVE device-mapper-multipath bug fix and enhancement update 2016-11-03 10:18:10 EDT

  None (edit)
Description Mike Christie 2016-06-20 22:05:52 EDT
Description of problem:

This is a request to merge the Ceph RBD multipathd path checker.

This is required by the ceph iSCSI HA project to support unclean failovers.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Mike Christie 2016-07-06 12:29:55 EDT
Just making a note about the patches needed for this bz:

Upstream commit:

commit b4d9ca8dc8bbfbd3782bf4cf2cb1a440685ccd07
Author: Hannes Reinecke <hare@suse.de>
Date:   Wed Nov 11 13:38:57 2015 +0100

    libmultipath: correctly initialize pp->sg_id

    The default SCSI protocol is 'SCSI_PROTOCOL_UNSPEC';
    '0' is SCSI_PROTOCOL_FCP.

    Signed-off-by: Hannes Reinecke <hare@suse.de>


and the final version of these patches:

https://www.redhat.com/archives/dm-devel/2016-July/msg00070.html
https://www.redhat.com/archives/dm-devel/2016-July/msg00071.html
https://www.redhat.com/archives/dm-devel/2016-July/msg00072.html
https://www.redhat.com/archives/dm-devel/2016-July/msg00073.html
Comment 11 Mike Christie 2016-10-18 16:02:59 EDT
Hey Steve,

Can we change the doc info so it does not sound like this is for general RBD use.

---
The multipath RBD support should only be used when you are sharing a RBD image, that has the exclusive-lock feature enabled, between multiple clients.
---

Basically, you cannot do fancy things people normally expect for multipath support like failover across network paths or round robin over multiple network paths. The support just handles failures on paths that are blacklisted due to another client taking the RBD exclusive-lock.
Comment 12 Steven J. Levine 2016-10-18 16:15:40 EDT
Mike:  I added your additional comment (just slightly edited) but I wasn't sure whether I need to go into detail on what this feature does not support.
Comment 13 Mike Christie 2016-10-18 16:33:24 EDT
Steve, what you have in comment #12 should be good.
Comment 15 errata-xmlrpc 2016-11-04 04:19:53 EDT
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-2016-2536.html

Note You need to log in before you can comment on or make changes to this bug.