[Linux-HA] heartbeat + drbd

Marc Boisis-Delavaud boisis at cines.fr
Fri Sep 1 07:23:53 MDT 2006


Robinson, Eric a écrit :
> If both are in a Secondary state, drbd is still not quite working. You have to resolve that before involving heartbeat. Have you issued the command to force one to become primary (--do-what-I-say)? If so, did it work? 
>   
I think drbd is working fine because when I force the primary (with 
--do-what-I-say) , I get this
/etc/init.d/drbd status
drbd driver loaded OK; device status:
version: 0.7.20 (api:79/proto:74)
SVN Revision: 2260 build by root at castor, 2006-07-26 13:30:03
 0: cs:Connected st:Primary/Secondary ld:Consistent
    ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0

but If I don't force it , nothing appen.
>
>
>
>
>
> Robinson, Eric a écrit :
>   
>> You said drbd is only starting on one node. I'm not sure if this will be helpful, but in my heartbeat/drbd environment, heartbeat does not actually start or stop drbd. Drbd starts as a normal system service. Heartbeat just manages it by issuing drbddisk commands to change drbd's state.
>>  
>> Have you managed to make drbd work outside of heartbeat? That's the first step.
>>   
>>     
> Ok , now I start drbd as a service at boot , so the two nodes are in secondary state.
> How can I configure cib to manage drbd state (primary/secondary), because  drbddisk is a V1 command and I'm using heartbeat V2 ?
>   
>> ________________________________
>>
>> From: linux-ha-bounces at lists.linux-ha.org on behalf of Marc Boisis-Delavaud
>> Sent: Wed 8/30/2006 2:20 AM
>> To: linux-ha at lists.linux-ha.org
>> Subject: [Linux-HA] heartbeat + drbd
>>
>>
>>
>> Hello,
>> I want to use heartbeat and drbd. When I start heatbeat only one node
>> start drbd, so my data aren't synchronised.
>> This is an extract of my cib.xml: Do you see anything wrong or missing ?
>>
>>
>> <primitive id="ldap_data" class="ocf" type="Filesystem"
>> provider="heartbeat">
>>          <instance_attributes id="ldap_data_instance_attrs">
>>            <attributes>
>>              <nvpair id="2f9748b6-8154-483f-a13b-65649cec9690"
>> name="device" value="/dev/drbd0"/>
>>              <nvpair id="efd525b4-aef3-44c5-a164-5fbd84535ed3"
>> name="directory" value="/ldap_data"/>
>>              <nvpair id="17faecb2-f3a0-46ce-9529-270ab29ac181"
>> name="fstype" value="ext3"/>
>>              <nvpair id="ldap_data_target_role" name="target_role"
>> value="started"/>
>>            </attributes>
>>          </instance_attributes>
>>          <operations/>
>>        </primitive>
>>        <primitive id="drbd" class="ocf" type="drbd" provider="heartbeat">
>>          <instance_attributes id="drbd_instance_attrs">
>>            <attributes>
>>              <nvpair id="drbd_target_role" name="target_role"
>> value="started"/>
>>              <nvpair id="2048ddb6-9cb9-4e73-b2e1-cf5108ced435"
>> name="drbd_resource" value="ldap"/>
>>            </attributes>
>>          </instance_attributes>
>>          <operations>
>>            <op id="b6669265-be8c-4ed2-b07f-0ba73e17f1fb" name="monitor"
>> interval="10s" timeout="60s"/>
>>          </operations>
>>        </primitive>
>>
>> --
>>     
>
>   




More information about the Linux-HA mailing list