[DRBD-user] Can't start DRBD service

[Maros Timko]

Just set wfc-timeout and possibly degr-wfc-timeout parameters in drbd.conf
to some reasonable numbers.

Tino

2009/6/13 Wilson Kwok <leiw324 at yahoo.com.hk>

>   Hello,
>
> I'm trying to test DRBD failover, so I poweroff node2 first and then node1.
> But I only can start up node2 DRBD service after bootup, what is that happen
> ?
>
> [root at node1 ~]# service drbd start
> Starting DRBD resources:    [ n(resource0) ].
> ..........
> ***************************************************************
>  DRBD's startup script waits for the peer node(s) to appear.
>  - In case this node was already a degraded cluster before the
>    reboot the timeout is 0 seconds. [degr-wfc-timeout]
>  - If the peer was available before the reboot the timeout will
>    expire after 0 seconds. [wfc-timeout]
>    (These values are for resource 'resource0'; 0 sec -> wait forever)
>  To abort waiting enter 'yes' [  15]:
>
> -----------------------------------------------------------------------------------------------------------------------
> /var/log/message
>
> Jun 13 20:31:09 node1 kernel: drbd0: conn( WFConnection -> Disconnecting )
> Jun 13 20:31:09 node1 kernel: drbd0: Discarding network configuration.
> Jun 13 20:31:09 node1 kernel: drbd0: tl_clear()
> Jun 13 20:31:09 node1 kernel: drbd0: Connection closed
> Jun 13 20:31:09 node1 kernel: drbd0: conn( Disconnecting -> StandAlone )
> Jun 13 20:31:09 node1 kernel: drbd0: receiver terminated
> Jun 13 20:31:09 node1 kernel: drbd0: Terminating receiver thread
> Jun 13 20:31:09 node1 kernel: drbd0: disk( UpToDate -> Diskless )
> Jun 13 20:31:09 node1 kernel: drbd0: drbd_bm_resize called with capacity ==
> 0
> Jun 13 20:31:09 node1 kernel: drbd0: worker terminated
> Jun 13 20:31:09 node1 kernel: drbd0: Terminating worker thread
> Jun 13 20:31:09 node1 kernel: drbd: module cleanup done.
> Jun 13 20:31:11 node1 kernel: drbd: initialised. Version: 8.0.13
> (api:86/proto:86)
> Jun 13 20:31:11 node1 kernel: drbd: GIT-hash:
> ee3ad77563d2e87171a3da17cc002ddfd1677dbe build by buildsvn at c5-i386-build,
> 2008-10-02 13:31:44
> Jun 13 20:31:11 node1 kernel: drbd: registered as block device major 147
> Jun 13 20:31:11 node1 kernel: drbd: minor_table @ 0xc7374a40
> Jun 13 20:31:12 node1 kernel: drbd0: disk( Diskless -> Attaching )
> Jun 13 20:31:12 node1 kernel: drbd0: Starting worker thread (from cqueue/0
> [176])
> Jun 13 20:31:12 node1 kernel: drbd0: Found 4 transactions (49 active
> extents) in activity log.
> Jun 13 20:31:12 node1 kernel: drbd0: max_segment_size ( = BIO size ) =
> 32768
> Jun 13 20:31:12 node1 kernel: drbd0: drbd_bm_resize called with capacity ==
> 995856
> Jun 13 20:31:12 node1 kernel: drbd0: resync bitmap: bits=124482 words=3892
> Jun 13 20:31:12 node1 kernel: drbd0: size = 486 MB (497928 KB)
> Jun 13 20:31:12 node1 kernel: drbd0: reading of bitmap took 0 jiffies
> Jun 13 20:31:12 node1 kernel: drbd0: recounting of set bits took additional
> 0 jiffies
> Jun 13 20:31:12 node1 kernel: drbd0: 28 KB (7 bits) marked out-of-sync by
> on disk bit-map.
> Jun 13 20:31:12 node1 kernel: drbd0: disk( Attaching -> UpToDate )
> Jun 13 20:31:12 node1 kernel: drbd0: Writing meta data super block now.
> Jun 13 20:31:12 node1 kernel: klogd 1.4.1, ---------- state change
> ----------
> Jun 13 20:31:12 node1 kernel: drbd0: conn( StandAlone -> Unconnected )
> Jun 13 20:31:12 node1 kernel: drbd0: Starting receiver thread (from
> drbd0_worker [5274])
> Jun 13 20:31:12 node1 kernel: drbd0: receiver (re)started
> Jun 13 20:31:12 node1 kernel: drbd0: conn( Unconnected -> WFConnection )
>
> Thanks
>
>  ------------------------------
> Yahoo!香港提供網上安全攻略，教你如何防範黑客!*了解更多* <http://hk.promo.yahoo.com/security/>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20090613/47b0460e/attachment.htm>