[DRBD-user] before-resync-target handler returned 3

Lars Ellenberg lars.ellenberg at linbit.com
Wed Jun 11 09:47:26 CEST 2008


On Tue, Jun 10, 2008 at 04:23:02PM +0200, P.Pijnacker wrote:
> My /etc/drbd.conf file is standard:
> 
> global {usage-count no;}
> common {
>   protocol C;
> }
> resource r0 {
>   on drbdtest1 {
>     device    /dev/drbd0;
>     disk      /dev/xendisks/drbd0;
>     address   192.168.10.101:7788;
>     meta-disk internal;
>   }
>   on drbdtest2 {
>     device    /dev/drbd0;
>     disk      /dev/xendisks/drbd0;
>     address   192.168.10.102:7788;
>     meta-disk internal;
>   }
> }
> 
> After create-md on both nodes I see both in Connected Secondary/Secondary
> state. 
> After "drbdadm -- --overwrite-data-of-peer primary r0" on one node, the
> other node immediately drops the connection and enters Standalone state. 
> On that node I looked in /var/log/messages:
> 
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: peer( Secondary -> Primary ) pdsk(
> Inconsistent -> UpToDate ) 
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: Writing meta data super block now.
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: Becoming sync target due to disk
> states.
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: Writing the whole bitmap, full sync
> required after drbd_sync_handshake.
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: Writing meta data super block now.
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: writing of bitmap took 1 jiffies
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: 7168 MB (1834943 bits) marked
> out-of-sync by on disk bit-map.
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: Writing meta data super block now.
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: conn( Connected -> WFBitMapT ) 
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: conn( WFBitMapT -> WFSyncUUID ) 
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: helper command: /sbin/drbdadm
> before-resync-target
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: before-resync-target handler
> returned 3, dropping connection.
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: peer( Primary -> Unknown ) conn(
> WFSyncUUID -> Disconnecting ) pdsk( UpToDate -> DUnknown ) 
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: Writing meta data super block now.
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: asender terminated
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: Terminating asender thread
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: tl_clear()
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: Connection closed
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: conn( Disconnecting -> StandAlone )
> 
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: receiver terminated
> Jun 10 15:57:34 drbdtest1 kernel: drbd0: Terminating receiver thread
> 
> It seems to me that a partial resync is the problem. Perhaps I can solve it
> bij forcing a full synchronisation. I don't know how.

my guess is that you upgraded your drbd module version,
but you did not upgrade your drbd userland (drbdadm/drbdsetup/drbdmeta).
install a matching drbd userland, and be happy.

-- 
: Lars Ellenberg                           http://www.linbit.com :
: DRBD/HA support and consulting             sales at linbit.com :
: LINBIT Information Technologies GmbH      Tel +43-1-8178292-0  :
: Vivenotgasse 48, A-1120 Vienna/Europe     Fax +43-1-8178292-82 :
__
please don't Cc me, but send to list -- I'm subscribed



More information about the drbd-user mailing list