[DRBD-user] RHCS node fencing with rhcs_fence & multiple volumes - resources staying DUnknown

Matt Willsher matt at monki.org.uk
Sat Oct 27 12:43:43 CEST 2012

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


On 27 October 2012 10:22, Lars Ellenberg <lars.ellenberg at linbit.com> wrote:
> On Thu, Oct 25, 2012 at 09:30:30PM +0100, Matt Willsher wrote:
>> I've been following Digimer's guide at
>> https://alteeve.ca/w/2-Node_Red_Hat_KVM_Cluster_Tutorial with a couple
>> of differences - I'm using DRBD 8.4.2-1 from ELrepo and Digimer's own
>> rhcs_fence script, currently 2.5.0. My configuration is (full output
>> of drbdadm dump is below) has three resources, two with two volumes
>
> Which is the problem, I guess.
> the get_local_resource_state() function in the rhcs_fence script
> assumes exactly one minor.
>
> But for multi-volume resources, a list of minor numbers is passed in.
>
> So grepping for /^ *"1 2 3 4 5":/ in /proc/drbd fails,
> it thinks it is not even UpToDate itself,
> and is then refusing to do anything else.

Yes that was it. I figured it out yesterday evening. The DRBD_MINOR
environmental variable, set by the process calling rhcs_fence,
contains a space delimited list, as you say. I've fixed rhcs_version
to cope with this, and that version is available at
https://github.com/mattwillsh/rhcs_fence with a pull request pending
(subject to regression testing by Digimer)  for merge into the
original code. I'm all up and running now.

Thanks,
Matt



More information about the drbd-user mailing list