[DRBD-user] Node01 not returning to primary after reboot

Cameron Smith velvetpixel at gmail.com
Fri Apr 2 03:19:31 CEST 2010

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


version: 8.0.16 (api:86/proto:86)

What would cause a node to not come back as primary after a reboot?
When it comes back up I get a Secondary/Secondary

 1: cs:Connected st:Secondary/Secondary ds:UpToDate/UpToDate C r---
    ns:1664 nr:636 dw:2400 dr:21135 al:16 bm:89 lo:0 pe:0 ua:0 ap:0
resync: used:0/61 hits:36 misses:6 starving:0 dirty:0 changed:6
act_log: used:0/127 hits:425 misses:16 starving:0 dirty:0 changed:16

In drbd.conf:
global {
  usage-count yes;
}
common {
  protocol C;
}
resource r0 {
  syncer {
    rate 110M;
  }
  on node1.example.com {
    device    /dev/drbd1;
    disk      /dev/sda5;
    address   10.0.114.2:7789;
    meta-disk /dev/sda6[0];
  }
  on node2.example.com {
    device    /dev/drbd1;
    disk      /dev/sda5;
    address   10.0.114.3:7789;
    meta-disk /dev/sda6[0];
  }
}

in Heartbeat:
node1.example.com drbddisk::r0 Filesystem::/dev/drbd1::/data::ext3
10.0.114.1 mysqld httpd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20100401/4753fa14/attachment.htm>


More information about the drbd-user mailing list