<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Massimo Cetra wrote:
<blockquote cite="mid:4A9674E2.9060409@navynet.it" type="cite"><br>
HI all,
<br>
<br>
i resume this old post that didn't have an answer.
<br>
I am experiencing the same identical problem.
<br>
<br>
the 2 nodes are 2 KVM virtual machines on 2.6.30.5 that are supposed to
work in dual primary mode with OCFS on top pf DRBD.
<br>
<br>
The testbed is:
<br>
- machines are up and running, synced and in dual primary mode.
<br>
<br>
- when i shutdown -h one of the two, everything comes up correctly.
<br>
- when i reboot (KVM is quite fast), i see that the rebooted node
doesn't sync and disconnects.
<br>
<br>
</blockquote>
<big>I am having almost the same problem with 8.3.2 I am running in
primary secondary mode. If I stop the secondary, the primary goes to
StandAlone and the log messages are the same as below. This does not
happen with 8.3.0. My nodes are physical not VMs.</big><br>
<br>
<blockquote cite="mid:4A9674E2.9060409@navynet.it" type="cite">This is
strange because i don't see any configuration problem.
<br>
If i restart drbd, it comes up cleanly as well.
<br>
<br>
How to fix and what's the problem ?
<br>
<br>
This is the relevant portion of the log.
<br>
<br>
[ 7.444342] drbd: initialised. Version: 8.3.2 (api:88/proto:86-90)
<br>
[ 7.466196] drbd: GIT-hash: dd7985327f146f33b86d4bff5ca8c94234ce840e
build by phil@fat-tyre, 2009-07-03 15:35:39
<br>
[ 7.489085] drbd: registered as block device major 147
<br>
[ 7.500701] drbd: minor_table @ 0xffff8800ddd5ac80
<br>
[ 7.523703] block drbd1: Starting worker thread (from cqueue [1691])
<br>
[ 7.535696] block drbd1: disk( Diskless -> Attaching )
<br>
[ 7.551927] block drbd1: Found 6 transactions (6 active extents) in
activity log.
<br>
[ 7.574272] block drbd1: Method to ensure write ordering: barrier
<br>
[ 7.585844] block drbd1: max_segment_size ( = BIO size ) = 32768
<br>
[ 7.597424] block drbd1: drbd_bm_resize called with capacity ==
104854328
<br>
[ 7.609724] block drbd1: resync bitmap: bits=13106791 words=204794
<br>
[ 7.632516] block drbd1: size = 50 GB (52427164 KB)
<br>
[ 7.647568] block drbd1: recounting of set bits took additional 0
jiffies
<br>
[ 7.659347] block drbd1: 0 KB (0 bits) marked out-of-sync by on disk
bit-map.
<br>
[ 7.671181] block drbd1: disk( Attaching -> UpToDate )
<br>
[ 7.682717] block drbd1: Barriers not supported on meta data device
- disabling
<br>
[ 7.773093] block drbd1: conn( StandAlone -> Unconnected )
<br>
[ 7.785603] block drbd1: Starting receiver thread (from drbd1_worker
[1698])
<br>
[ 7.808437] block drbd1: receiver (re)started
<br>
[ 7.824425] block drbd1: conn( Unconnected -> WFConnection )
<br>
[ 7.836513] block drbd1: bind before connect failed, err = -99
<br>
[ 7.852925] block drbd1: conn( WFConnection -> Disconnecting )
<br>
[ 7.868108] block drbd1: role( Secondary -> Primary )
<br>
[ 7.880114] block drbd1: Creating new current UUID
<br>
[ 8.064182] block drbd1: Discarding network configuration.
<br>
[ 8.075792] block drbd1: Connection closed
<br>
[ 8.087158] block drbd1: conn( Disconnecting -> StandAlone )
<br>
[ 8.098898] block drbd1: receiver terminated
<br>
[ 8.110451] block drbd1: Terminating receiver thread
<br>
<br>
Thanks,
<br>
Max
<br>
<br>
<br>
<br>
Richard Hector ha scritto:
<br>
<blockquote type="cite">Hi all,
<br>
<br>
One of my 2 machines doesn't seem to connect at boot time - doesn't
<br>
matter whether it's configured to come up as primary or secondary.
This,
<br>
at a guess, seems relevant:
<br>
<br>
...
<br>
[ 29.196417] drbd0: conn( Unconnected -> WFConnection ) [
29.196417] drbd0: bind before connect failed, err = -99
<br>
[ 29.196417] drbd0: conn( WFConnection -> Disconnecting ) ...
<br>
<br>
I've tried to find any docs regarding this without success - that bind
<br>
is an internal kernel one, not bind(2) (the syscall), right? My
<br>
expertise at navigating the kernel source is rather limited ...
<br>
<br>
If I run /etc/init.d/drbd restart after boot, it comes up fine.
<br>
<br>
Both machines are Debian Lenny, amd64, with drbd 8.3 from
backports.org.
<br>
<br>
Any suggestions? Any more useful info I can supply?
<br>
</blockquote>
<br>
<br>
_______________________________________________
<br>
drbd-user mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:drbd-user@lists.linbit.com">drbd-user@lists.linbit.com</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.linbit.com/mailman/listinfo/drbd-user">http://lists.linbit.com/mailman/listinfo/drbd-user</a>
<br>
<br>
</blockquote>
<br>
</body>
</html>