[DRBD-user] drbd.ocf misinterpreting role status with multiple volumes

Lars Ellenberg lars.ellenberg at linbit.com
Tue Aug 25 18:05:03 CEST 2015

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

On Mon, Aug 24, 2015 at 10:59:52PM +0200, Matthias Ferdinand wrote:
> On Sat, Aug 22, 2015 at 12:00:01PM +0200, drbd-user-request at lists.linbit.com wrote:
> > Date: Sat, 22 Aug 2015 11:29:37 +0200
> > From: Lars Ellenberg <lars.ellenberg at linbit.com>
> > Subject: Re: [DRBD-user] drbd.ocf misinterpreting role status with
> > 	multiple volumes
> > 
> > ...
> > Yes, that is the case, and the above is intentional.
> > Though I don't remember all of the reasoning right now.  Probably has
> > something to do with adding a volume to an existing resource.
> > 
> > If you want independent volumes, use independend resources.
> nope, we like the writer order guarantee :-)
> > Pacemaker would not have any way to deal with a "partially promoted" DRBD.
> too bad. If the RA knew the supposed role, it could try to achieve that
> during a monitor. Though a monitor that actively changes stuff might be
> a bit surprising.
> > Anyone cares enough to prepare a patch?
> I attached a patch (for 8.4.4, which is the version we are using). It
> returns OCF_FAILED_MASTER in a monitor operation, but leaves the rc of
> the internal drbd_status untouched. Otherwise all drbd_status()
> consumers would need to handle that extra case.
> Note that it also returns OCF_FAILED_MASTER if the resource is supposed
> to be in Secondary role and one subvolume is Primary (showing as "Slave"
> in crm_mon).

Great. Thanks.

Please allow a couple of weeks for (a variant of) this
to "propagate" into public git.


More information about the drbd-user mailing list