<div dir="ltr">My system is a 2.1.4 heartbeat cluster with rh el 5.2.<br>I have 2.x config enabled (with crm = on) on it.<br>I have installed kmod-drbd82-8.2.6-1.2.6.18_92.el5 and drbd82-8.2.6-1.el5.centos<br>drbd module is started itself before heartbeat and I use drbdisk resource script in heartbeat to manage it.<br>
If primary node is up and I shutdown the second, on the primary I get some change status steps with <br>connection: Connected -> NetworkFailure -> Unconnected -> WFConnection<br>state of peer: Secondary -> Unknown<br>
peer disk: DUnknown -> Outdated<br>(because outdate-peer helper returned 5 (peer is unreachable, assumed to be dead)<br><br>so that the final status on the primary is<br><br>[root@nfsnode1 ~]# service drbd status<br>drbd driver loaded OK; device status:<br>
version: 8.2.6 (api:88/proto:86-88)<br>GIT-hash: 3e69822d3bb4920a8c1bfdf7d647169eba7d2eb4 build by buildsvn@c5-i386-build, 2008-06-21 08:29:11<br>m:res cs st ds p mounted fstype<br>
0:drbd-resource-0 WFConnection Primary/Unknown UpToDate/Outdated C /drbd0 ext3<br><br>When I restart nfsnode1 (keeping nfsnode2 powered off) I would expect during drbd startup that degr-wfc-timeout will take place.<br>
Instead it seems that wfc-timeout is the parameter followed: with wfc-timeout set to 0 no start at all, with it put to 30 seconds, after 30 seconds drbd starts, and then heartbeat correctly.<br>So the question is: when drbd thinks it is in degraded mode?<br>
or does it depends on the fact that heartbeat stop during shutdown puts it in Secondary mode?<br><br>Thanks,<br>Gianluca<br><br><br><br></div>