[DRBD-user] Question about Drbd/Server Reboots

[aeternaleto]

I currently have drbd installed on two servers.

I've noticed with i reboot both servers, the primary and secondary, that one
does not take ownership upon bootup and I end up having to run this

drbdadm -- --overwrite-data-of-peer primary repdata
drbdadm -- --overwrite-data-of-peer primary repdata1

Is there something that I am missing to specify with machine is the primary
during bootup?

My Drbd.conf is listed below:


##App##
global { usage-count no; }
resource repdata {
  protocol C;
  startup { wfc-timeout 0; degr-wfc-timeout     120; }
  disk { on-io-error detach; } # or panic, ...
  net {  cram-hmac-alg "sha1"; shared-secret "Z792CK5W"; } # don't forget to
choose a secret for auth !
  syncer { rate 100M; }
  on filer1 {
    device /dev/drbd0;
    disk /dev/sdb1;
    address 10.0.0.110:7788;
    meta-disk internal;
  }
  on filer2 {
    device /dev/drbd0;
    disk /dev/sdb1;
    address 10.0.0.112:7788;
    meta-disk internal;
  }

}

##MLSData##
resource repdata1 {
  protocol C;
  startup { wfc-timeout 0; degr-wfc-timeout     120; }
  disk { on-io-error detach; } # or panic, ...
  net {  cram-hmac-alg "sha1"; shared-secret "Z792CK5W"; } # don't forget to
choose a secret for auth !
  syncer { rate 100M; }
on filer1 {
   device /dev/drbd1;
   disk /dev/sdb2;
   address 10.0.0.110:7789;
   meta-disk internal;
}
on filer2 {
   device /dev/drdb1;
   disk /dev/sdb2;
   address 10.0.0.112:7789;
    meta-disk internal;
  }
}

-- 
View this message in context: http://www.nabble.com/Question-about-Drbd-Server-Reboots-tp16452420p16452420.html
Sent from the DRBD - User mailing list archive at Nabble.com.