[DRBD-user] Stuck after going from Connected -> WFBitMapS/WFBitMapT

divyesh divyesh at netzary.com
Wed May 30 10:42:39 CEST 2012

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


Dear All,

I am trying to setup DRBD by following the article at

http://www.howtoforge.com/setting-up-network-raid1-with-drbd-on-ubuntu-11.10-p2

I am using
Ubuntu 10.04
DRBD - 8.3.7

In the first run I had everything working perfectly and when shifting 
the systems to a production environment I decided to restart the Meta 
Data creation part and start from scratch. The IP's had changed entirely 
in the production environment.

Issuing drdbadm create-md r0 in both the servers runs successfully. But 
when I do "drbdadm -- --overwrite-data-of-peer primary all" on the 
primary it fails to start the re sync.

My config file is as given below

resource r0 {
     protocol C;
     syncer {
         rate 50M;
     }
     startup {
         wfc-timeout 15;
         degr-wfc-timeout 60;
     }
     net {
         cram-hmac-alg sha1;
         shared-secret "aklsadkjlhdbskjndsf8738734jkfkjfkjf";
     }
     on primaryds {
         device /dev/drbd0;
         disk /dev/md2;
         address 172.16.7.1:7788;
         meta-disk internal;
     }
     on secondaryds {
         device /dev/drbd0;
         disk /dev/md2;
         address 172.16.7.3:7788;
         meta-disk internal;
     }
}


Status on primary

root at primaryds:~# cat /proc/drbd
version: 8.3.7 (api:88/proto:86-91)
GIT-hash: ea9e28dbff98e331a62bcbcc63a6135808fe2917 build by 
root at primaryds, 2012-05-12 15:08:01
  0: cs:WFBitMapS ro:Primary/Secondary ds:UpToDate/Inconsistent C r----
     ns:0 nr:0 dw:0 dr:200 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b 
oos:5690352828


Status on secondary

root at secondaryds:/etc/drbd.d# cat /proc/drbd
version: 8.3.7 (api:88/proto:86-91)
GIT-hash: ea9e28dbff98e331a62bcbcc63a6135808fe2917 build by 
root at secondaryds, 2012-05-12 15:25:25
  0: cs:WFBitMapT ro:Secondary/Primary ds:Inconsistent/UpToDate C r----
     ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b 
oos:5690352828


Log of Primary

May 30 13:42:23 primaryds kernel: [ 1584.057076] block drbd0: role( 
Secondary -> Primary ) disk( Inconsistent -> UpToDate )
May 30 13:42:23 primaryds kernel: [ 1584.086264] block drbd0: Forced to 
consider local data as UpToDate!
May 30 13:42:23 primaryds kernel: [ 1584.086303] block drbd0: Creating 
new current UUID
May 30 13:42:26 primaryds kernel: [ 1586.405551] block drbd0: 
drbd_sync_handshake:
May 30 13:42:26 primaryds kernel: [ 1586.405564] block drbd0: self 
E8A075F378173D4B:0000000000000004:0000000000000000:0000000000000000 
bits:1422588207 flags:0
May 30 13:42:26 primaryds kernel: [ 1586.405574] block drbd0: peer 
0000000000000004:0000000000000000:0000000000000000:0000000000000000 
bits:1422588207 flags:0
May 30 13:42:26 primaryds kernel: [ 1586.405582] block drbd0: 
uuid_compare()=2 by rule 30
May 30 13:42:26 primaryds kernel: [ 1586.405587] block drbd0: Becoming 
sync source due to disk states.
May 30 13:42:26 primaryds kernel: [ 1586.405592] block drbd0: Writing 
the whole bitmap, full sync required after drbd_sync_handshake.
May 30 13:42:27 primaryds kernel: [ 1588.171638] block drbd0: 5427 GB 
(1422588207 bits) marked out-of-sync by on disk bit-map.
May 30 13:42:27 primaryds kernel: [ 1588.172769] block drbd0: conn( 
Connected -> WFBitMapS )

Log in Secondary

May 30 13:42:24 secondaryds kernel: [ 1563.304894] block drbd0: peer( 
Secondary -> Primary ) pdsk( Inconsistent -> UpToDate )
May 30 13:42:24 secondaryds kernel: [ 1563.339674] block drbd0: 
drbd_sync_handshake:
May 30 13:42:24 secondaryds kernel: [ 1563.339685] block drbd0: self 
0000000000000004:0000000000000000:0000000000000000:0000000000000000 
bits:1422588207 flags:0
May 30 13:42:24 secondaryds kernel: [ 1563.339695] block drbd0: peer 
E8A075F378173D4B:0000000000000004:0000000000000000:0000000000000000 
bits:1422588207 flags:0
May 30 13:42:24 secondaryds kernel: [ 1563.339703] block drbd0: 
uuid_compare()=-2 by rule 20
May 30 13:42:24 secondaryds kernel: [ 1563.339709] block drbd0: Becoming 
sync target due to disk states.
May 30 13:42:24 secondaryds kernel: [ 1563.339714] block drbd0: Writing 
the whole bitmap, full sync required after drbd_sync_handshake.
May 30 13:42:26 secondaryds kernel: [ 1565.652342] block drbd0: 5427 GB 
(1422588207 bits) marked out-of-sync by on disk bit-map.
May 30 13:42:26 secondaryds kernel: [ 1565.652965] block drbd0: conn( 
Connected -> WFBitMapT )


The serves are now stuck like this. Tried redoing it couple of time but 
noting happens.

Why could the resync not be taking place.

Regards,
Divyesh




More information about the drbd-user mailing list