Hi,<br>
<br>
I am using drbd-8.0_pre1. When secondary
goes down (rcdrbd stop) and comes up again (rcdrbd start) I get this:<br>
drbd driver loaded OK; device status:<br>
version: 8.0_pre1 (api:80/proto:80)<br>
SVN Revision: 2121 build by root@my-host1, 2006-03-15 11:20:22<br>
0: cs:SyncTarget st:Secondary/Primary ds:Inconsistent/UpToDate<br>
ns:0 nr:1110816 dw:1110816 dr:0 al:0 bm:67 lo:2 pe:7 ua:2 ap:0<br>
[====>...............] sync'ed: 21.3% (4037/5122)M<br>
finish: 0:06:19 speed: 10,860 (10,284) K/sec<br>
resync: used:1/7 hits:69363 misses:68 starving:0 dirty:0 changed:68<br>
act_log: used:0/257 hits:0 misses:0 starving:0 dirty:0 changed:0<br>
<br>
Relevant syslog msgs are as follows:<br>
<br>
drbd: registered as block device major 147<br>
drbd0: disk( Diskless -> Attaching )<br>
drbd0: drbd_bm_resize called with capacity == 10489976<br>
drbd0: bits = 1311247 in /usr/src/drbd-8.0_pre1/drbd/drbd_bitmap.c:369<br>
drbd0: resync bitmap: bits=1311247 words=40978<br>
drbd0: size = 5122 MB (5244988 KB)<br>
drbd0: reading of bitmap took 1 jiffies<br>
drbd0: recounting of set bits took additional 0 jiffies<br>
drbd0: 5122 MB marked out-of-sync by on disk bit-map.<br>
drbd0: Found 6 transactions (10 active extents) in activity log.<br>
drbd0: disk( Attaching -> Consistent )<br>
drbd0: Writing meta data super block now.<br>
drbd0: conn( StandAlone -> Unconnected )<br>
drbd0: conn( Unconnected -> WFConnection )<br>
drbd0: conn( WFConnection -> WFReportParams )<br>
drbd0: Handshake successful: DRBD Network Protocol version 80<br>
drbd0: peer( Unknown -> Primary ) conn( WFReportParams ->
WFBitMapT ) disk( Consistent -> Outdated ) pdsk( DUnknown ->
UpToDate )<br>
drbd0: Writing meta data super block now.<br>
drbd0: conn( WFBitMapT -> WFSyncUUID )<br>
drbd0: conn( WFSyncUUID -> SyncTarget ) disk( Outdated -> Inconsistent )<br>
drbd0: Began resync as SyncTarget (will sync 5244988 KB [1311247 bits set]).<br>
drbd0: Writing meta data super block now.<br>
<br>
If the primary goes down and comes up again, however no full sync happens. drbd just comes up as secondary.<br>
<br>
I thought with activity logs & resync bitmaps full-sync was a thing of the past. Is something wrong on my setup? <br>
<br>
drbdadm dump is as follows:<br>
<br>
common {<br>
syncer {<br>
rate 10M;<br>
}<br>
}<br>
<br>
resource r0 {<br>
protocol C;<br>
on my-host1 {<br>
device /dev/drbd0;<br>
disk
/dev/sda7;<br>
address <a href="http://192.168.131.96:7788">192.168.131.96:7788</a>;<br>
meta-disk internal;<br>
}<br>
on my-host2 {<br>
device /dev/drbd0;<br>
disk
/dev/sda7;<br>
address <a href="http://192.168.131.97:7788">192.168.131.97:7788</a>;<br>
meta-disk internal;<br>
}<br>
net {<br>
after-sb-0pri disconnect;<br>
after-sb-1pri disconnect;<br>
after-sb-2pri disconnect;<br>
}<br>
disk {<br>
on-io-error detach;<br>
}<br>
syncer {<br>
rate 10M;<br>
al-extents 257;<br>
}<br>
startup {<br>
degr-wfc-timeout 120;<br>
}<br>
handlers {<br>
pri-on-incon-degr "halt -f";<br>
pri-lost-after-sb "halt -f";<br>
outdate-peer "/usr/lib/drbd/outdate-peer.sh on
amd <a href="http://192.168.22.11">192.168.22.11</a> <a href="http://192.168.23.11">192.168.23.11</a> on alf <a href="http://192.168.22.12">192.168.22.12</a> <a href="http://192.168.23.12">192.168.23.12</a>";<br>
}<br>
}<br>
<br>
Rgds<br>
dhairesh<br>