[DRBD-user] DRBD doing full sync when secondary goes down and comes up again

[Oza Dhairesh]

Hi,

      I am using drbd-8.0_pre1. When secondary goes down (rcdrbd stop) and
comes up again (rcdrbd start) I get this:
drbd driver loaded OK; device status:
version: 8.0_pre1 (api:80/proto:80)
SVN Revision: 2121 build by root at my-host1, 2006-03-15 11:20:22
 0: cs:SyncTarget st:Secondary/Primary ds:Inconsistent/UpToDate
    ns:0 nr:1110816 dw:1110816 dr:0 al:0 bm:67 lo:2 pe:7 ua:2 ap:0
        [====>...............] sync'ed: 21.3% (4037/5122)M
        finish: 0:06:19 speed: 10,860 (10,284) K/sec
        resync: used:1/7 hits:69363 misses:68 starving:0 dirty:0 changed:68
        act_log: used:0/257 hits:0 misses:0 starving:0 dirty:0 changed:0

Relevant syslog msgs are as follows:

drbd: registered as block device major 147
drbd0: disk( Diskless -> Attaching )
drbd0: drbd_bm_resize called with capacity == 10489976
drbd0: bits = 1311247 in /usr/src/drbd-8.0_pre1/drbd/drbd_bitmap.c:369
drbd0: resync bitmap: bits=1311247 words=40978
drbd0: size = 5122 MB (5244988 KB)
drbd0: reading of bitmap took 1 jiffies
drbd0: recounting of set bits took additional 0 jiffies
drbd0: 5122 MB marked out-of-sync by on disk bit-map.
drbd0: Found 6 transactions (10 active extents) in activity log.
drbd0: disk( Attaching -> Consistent )
drbd0: Writing meta data super block now.
drbd0: conn( StandAlone -> Unconnected )
drbd0: conn( Unconnected -> WFConnection )
drbd0: conn( WFConnection -> WFReportParams )
drbd0: Handshake successful: DRBD Network Protocol version 80
drbd0: peer( Unknown -> Primary ) conn( WFReportParams -> WFBitMapT ) disk(
Consistent -> Outdated ) pdsk( DUnknown -> UpToDate )
drbd0: Writing meta data super block now.
drbd0: conn( WFBitMapT -> WFSyncUUID )
drbd0: conn( WFSyncUUID -> SyncTarget ) disk( Outdated -> Inconsistent )
drbd0: Began resync as SyncTarget (will sync 5244988 KB [1311247 bits set]).
drbd0: Writing meta data super block now.

If the primary goes down and comes up again, however no full sync happens.
drbd just comes up as secondary.

I thought with activity logs & resync bitmaps full-sync was a thing of the
past. Is something wrong on my setup?

drbdadm dump is as follows:

common {
    syncer {
        rate             10M;
    }
}

resource r0 {
    protocol               C;
    on my-host1 {
        device           /dev/drbd0;
        disk             /dev/sda7;
        address          192.168.131.96:7788;
        meta-disk        internal;
    }
    on my-host2 {
        device           /dev/drbd0;
        disk             /dev/sda7;
        address          192.168.131.97:7788;
        meta-disk        internal;
    }
    net {
        after-sb-0pri    disconnect;
        after-sb-1pri    disconnect;
        after-sb-2pri    disconnect;
    }
    disk {
        on-io-error      detach;
    }
    syncer {
        rate             10M;
        al-extents       257;
    }
    startup {
        degr-wfc-timeout 120;
    }
    handlers {
        pri-on-incon-degr "halt -f";
        pri-lost-after-sb "halt -f";
        outdate-peer     "/usr/lib/drbd/outdate-peer.sh on amd 192.168.22.11
192.168.23.11 on alf 192.168.22.12 192.168.23.12";
    }
}

Rgds
dhairesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20060510/cd64ecba/attachment.htm>