[DRBD-user] "drbdadm up al" generates a segmentation fault - any idea why ?

[Ian Brown]

Hello,

One machine A I had built drbd from source  (drbd-8.0.1).
This machine has 2.6.20 linux kernel.


Now, I ran :
 for i in `seq 0 15` ; do mknod -m 0660 /dev/drbd$i b 147 $i; done

Than on this machine I performed:
modprobe drbd

and then :

in drbd.conf I have :

skip {
}

global {
    usage-count yes;
}


common {
  syncer { rate 10M; }
}

resource cluster {

  protocol C;

  handlers {
    pri-on-incon-degr "echo o > /proc/sysrq-trigger ; halt -f";
    pri-lost-after-sb "echo o > /proc/sysrq-trigger ; halt -f";
    local-io-error "echo o > /proc/sysrq-trigger ; halt -f";
    outdate-peer "/usr/sbin/drbd-peer-outdater";
  }

  startup {
    degr-wfc-timeout 120;    # 2 minutes.
  }

  disk {
    on-io-error   detach;
  }

  net {
    after-sb-0pri disconnect;
    after-sb-1pri disconnect;
    after-sb-2pri disconnect;
    rr-conflict disconnect;
  }

  syncer {
    rate 10M;

    after "r2";

    al-extents 257;
  }

  on myhost {
    device    /dev/drbd0;
    disk      /dev/sda7;
    address   192.168.0.190:7788;
    meta-disk internal;
  }
}



where myhost is defined in /etc/hosts and has
IP address of 192.168.0.190.
Let's call this machine (myhost), with the 192.168.0.190 IP address, machine B.


/dev/sda7 on machine B  is an ext3 filesystem (which is mounted).

Now, when I run , from machine A , "drbdadm up all",
I get Segmentation fault (core dumped).

I am aware that there are ususally two nodes in the drbd.conf file,
but is it a must ? could it be that because there is only one node
there is a problem here ?

Any idea what could be wrong here ?


Ian