[DRBD-user] How to reproduce 0.7.24 behavior in 8.3.1

Maxim Vladimirsky horkhe at gmail.com
Mon May 25 13:53:58 CEST 2009

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

Hi Everybody,

We have been using DRBD 0.7.24 for very long time. But the time for upgrade
has finally come. So DRBD 8.3.1 was installed and drbd.conf adjusted.
However now DRBD behaves differently when primary node gets rebooted. When
we were running DRBD 0.7.24 and the primary node went down the secondary one
took over primary role, and when the faulty node got up it became secondary.
Now when we are running DRBD 8.3.1 if primary node goes down the secondary
one still takes over, but when the faulty node gets up, both nodes go in
stand-alone mode breaking the cluster in pieces.

I guess that we made a mistake in our drbd.conf file. Could please someone
advise where it is. Our configuration file is as follows:

global {
    usage-count no;
resource shared {
    protocol C;
    handlers {
        pri-on-incon-degr "echo '!DRBD! pri on incon-degr' | wall ; sleep 15
; halt -f";
    startup {
        wfc-timeout 1;
        degr-wfc-timeout 1;
        outdated-wfc-timeout 1;
    disk {
        on-io-error detach;
    net {
        timeout 60;
        sndbuf-size 1M;
        connect-int 10;
        ping-int 10;
        max-buffers 4096;
        max-epoch-size 2048;
        ko-count 4;
        after-sb-0pri discard-younger-primary;
        after-sb-1pri consensus;
        after-sb-2pri disconnect;
    syncer {
        rate 100M;
        al-extents 1017;
    device /dev/drbd0;
    disk /dev/sda9;
    meta-disk /dev/sda8[0];
    on node1 {
    on node2 {

Thank you in advance,
Maxim Vladimirsky
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20090525/803b3514/attachment.htm>

More information about the drbd-user mailing list