> Ryan,
>
> I switched to "lsb drbd" and hb_gui can finally see drbd service ...
> that's
> good part.
> Bad part is that drbd service is still in Secondary/Secondary state. Looks
> like HB didn't make any of them primary.
>
> What I am missing?
What does the XML for your LSB drbd resource agents looks like?
Since you mention your devices are Secondary/Secondary, I assume drbd
started fine and that it's all working. Can you manually force the state
change with drbdadm from one of the nodes?
Your XML should be something like this:
<primitive id="my_drbd" class="heartbeat" type="drbddisk"
provider="heartbeat">
<instance_attributes id="my_drbd_instance_attrs">
<attributes>
<nvpair id="my_drbd_target_role" name="target_role"
value="started"/>
<nvpair id="d44b1af0-2af8-4e3b-895b-f027752ce604" name="1"
value="drbddevname"/>
</attributes>
</instance_attributes>
<operations>
<op id="519a0efa-92bb-4298-9c00-c4aac2884e0b" name="monitor"
interval="30s" timeout="15s" start_delay="15s"
disabled="false" on_fail="restart"/>
</operations>
</primitive>
Where "drbddevname" is the DRBD device name that you have configured in
drbd.conf for this particular drbd device. I created this XML with hb_gui.
You then, of course, use a Filesystem RA to mount the fs from the drbd
system device, usually /dev/drbd1,2,3,4,etc.
--Ryan
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
