I'am testing heartbeat with DRBD.
I have 3 resources :
ms_drbd0
+ r_drbd0:0
+ r_drbd0:1
r_fs
r_xterm_drbd
linked by various constraints (cf. my CIB).
When a failover occurs (on a r_drbd0 error) :
- the DRBD resource is migrated on an other node (and declared "down" on
the failed node)
- the DRBD resource on the failed node seams to be blocked (not
monitored and not managed)
When the DRBD resource (previously failed) is usable again (drbdsetup
/dev/drbd0 secondary) heartbeat do not change the resource state (blocked).
Is there any way to monitor DRBD after a failure ?
Because after a failure as the DRBD resource is "down" on the failed
node, the data are not mirrored and in my opinion "high availability" is
not provided.
In case of a node failure (on the new DRBD primary node) data are lost
and the DRBD could not be started.
Is there any way not to block a drbd resource on a node in case of failure ?
Thanks for your answers.
---
Sylvain.
<cib admin_epoch="0" have_quorum="true" ignore_dtd="false" num_peers="2" cib_feature_revision="1.3" ccm_transition="2" generated="true" dc_uuid="7f6c552b-1605-41d9-817c-08daf6ef0e4c" epoch="1361" num_updates="1" cib-last-written="Wed Jan 30 17:30:58 2008">
<configuration>
<crm_config>
<cluster_property_set id="cib-bootstrap-options">
<attributes>
<nvpair id="cib-bootstrap-options-last-lrm-refresh" name="last-lrm-refresh" value="1201710596"/>
</attributes>
</cluster_property_set>
</crm_config>
<nodes>
<node id="7f6c552b-1605-41d9-817c-08daf6ef0e4c" uname="anaisrh4-2" type="normal"/>
<node id="775e6f3f-520f-4cb8-b39e-a03023a15601" uname="anaisrh4-1" type="normal"/>
</nodes>
<resources>
<master_slave id="ms_drbd0" restart_type="restart">
<meta_attributes id="ma-ms-drbd0">
<attributes>
<nvpair id="ma-ms-drbd0-1" name="clone_max" value="2"/>
<nvpair id="ma-ms-drbd0-2" name="clone_node_max" value="1"/>
<nvpair id="ma-ms-drbd0-3" name="master_max" value="1"/>
<nvpair id="ma-ms-drbd0-4" name="master_node_max" value="1"/>
<nvpair id="ma-ms-drbd0-5" name="notify" value="yes"/>
<nvpair id="ma-ms-drbd0-6" name="globally_unique" value="false"/>
</attributes>
</meta_attributes>
<primitive id="r_drbd0" class="ocf" provider="heartbeat" type="drbd">
<instance_attributes id="ia-drbd0">
<attributes>
<nvpair id="ia-drbd0-1" name="drbd_resource" value="drbd0"/>
<nvpair id="r_drbd0:0_target_role" name="target_role" value="started"/>
</attributes>
</instance_attributes>
<operations>
<op id="op-ms-drbd2-1" name="monitor" interval="60s" timeout="60s" start_delay="30s" role="Master"/>
<op id="op-ms-drbd2-2" name="monitor" interval="61s" timeout="60s" start_delay="30s" role="Slave"/>
</operations>
</primitive>
<instance_attributes id="ms_drbd0_instance_attrs">
<attributes>
<nvpair id="ms_drbd0_target_role" name="target_role" value="stopped"/>
</attributes>
</instance_attributes>
</master_slave>
<primitive class="ocf" provider="heartbeat" type="Filesystem" id="r_fs">
<instance_attributes id="ia-fs0">
<attributes>
<nvpair id="ia-fs0-1" name="fstype" value="ext3"/>
<nvpair name="directory" id="ia-fs0-2" value="/mnt/drbd0"/>
<nvpair id="ia-fs0-3" name="device" value="/dev/drbd0"/>
<nvpair id="r_fs_target_role" name="target_role" value="started"/>
</attributes>
</instance_attributes>
<operations>
<op id="fs0-monitor0" name="monitor" interval="60s" timeout="120s" start_delay="1m"/>
</operations>
</primitive>
<primitive class="ocf" type="XtermDrbd" provider="thales" id="r_xterm_drbd">
<instance_attributes id="r_xterm_drbd_instance_attrs">
<attributes>
<nvpair name="target_role" id="r_xterm_drbd_target_role" value="started"/>
</attributes>
</instance_attributes>
<operations>
<op id="r_xterm_drbd_monitor" interval="2s" name="monitor" timeout="10s" start_delay="3" disabled="false"/>
</operations>
</primitive>
</resources>
<constraints>
<rsc_order id="order_drbd_fs" from="r_fs" action="start" to="ms_drbd0" to_action="promote" type="after"/>
<rsc_colocation id="coloc_fs_drbd" to="ms_drbd0" to_role="master" from="r_fs" score="INFINITY"/>
<rsc_colocation id="coloc_xterm_fs" to="r_fs" from="r_xterm_drbd" score="INFINITY"/>
<rsc_order id="order_fs_xterm" from="r_xterm_drbd" action="start" type="after" to="r_fs"/>
</constraints>
</configuration>
</cib>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
