[DRBD-user] DRBD Failover Not Working after Cold Shutdown of Primary

Art Age Software artagesw at gmail.com
Mon Jan 7 22:16:16 CET 2008

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

Hi all,

I've asked this question before and have still not figured it out.

Either  the degr-wfc-timeout setting is not working as documented, or
I just don't understand how it is supposed to work.

Here's the scenario:

1) Both primary and secondary nodes (servers) are running. DRBD is
primary/connected/uptodate on Node1 and secondary/connected/uptodate
on Node2.

2) Shut down Node2. This takes DRBD on Node1 into primary/disconnected state.

3) Reboot Node1. (Do **not** start up Node2. It remains shut down.)

According to my understanding, what I now have is a "degraded
cluster." However, when Node1 reboots, the init script waits forever,
ignoring the degr-wfc-timeout setting. It is as if DRBD does not think
the cluster is degraded.

Another DRBD user on the list has confirmed seeing this behavior as
well in his setup.

So, is this a DRBD bug? Or am I misunderstanding the use of the
degr-wfc-timeout setting?



More information about the drbd-user mailing list