[DRBD-user] degr-wfc-timeout - when is this value used?

[Werner Fischer]

Hi all,

I have degr-wfc-timeout set to 120, and tested it like Philipp described
it in this post:
http://lists.linbit.com/pipermail/drbd-user/2004-August/001674.html

Initially, the cluster was running fine with services on node1 (so DRBD
primary on node1, secondary on node2). I pulled the power cables from
node2 -> so the cluster got degraded. Then I tried to reboot node1
(using 'reboot' command) to see whether degr-wfc-timeout gets active or
not. I expected DRBD to continue on boot after 120 seconds waiting. But
it kept on waiting (I think because of wfc-timeout is on it's default
value 0, which means unlimited).
I did the same test again with pulling power cables on node1 (when it
was an degraded cluster) instead of executing 'reboot' - but also in
this case node1 kept on waiting unlimited...

The manpage (man drbd.conf) says:
---------------------------------------------------------------------
       wfc-timeout time
              Wait for connection timeout.  The init script  drbd(8)
              blocks  the  boot process until the DRBD resources are
              connected.  This is so when the cluster manager starts
              later, it does not see a resource with internal split-
              brain.  In case you want to limit the wait time, do it
              here.   Default  is  0, which means unlimited. Unit is
              seconds.

       degr-wfc-timeout time
              Wait for  connection  timeout,  if  this  node  was  a
              degraded cluster.  In case a degraded cluster (= clus-
              ter with only one node left) is rebooted, this timeout
              value is used instead of wfc-timeout, because the peer
              is less likely to show up in time, if it had been dead
              before.  Default is 60, unit is seconds. Value 0 means
              unlimited.
---------------------------------------------------------------------

Is my experienced behaviour the expected one?

regards,
Werner

PS: I'm using drbd 0.7.15, CentOS4.2, this is my /etc/drbd.conf:

resource r0 {
  protocol C;
  incon-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ; sleep 60 ;
halt -f";    

  startup {
    degr-wfc-timeout 120;   
  }

  net {
    on-disconnect reconnect;
  }

  disk {
    on-io-error   detach;
  }

  syncer {
    rate 30M;
    group 1;
    al-extents 257;     
  }

  on node1 {
    device     /dev/drbd0;
    disk       /dev/sda4;
    address    192.168.255.1:7788;
    meta-disk  internal;    
  }

  on node2 {
    device     /dev/drbd0;
    disk       /dev/sda4;
    address    192.168.255.2:7788;
    meta-disk  internal;  
  }

}