Maybe you need to bring your network up before drbd?
->Apr 7 16:15:05 xenpool12 kernel: block drbd1: bind before connect
failed, err = -99
M.
Phil Stricker wrote:
Hi!
I am using two XenServer 5.5 with a dual-primary drbd storage.
At the moment, i am having one problem:
If i reboot one of the servers, the ressource does not reconnect after
the reboot:
1: cs:StandAlone ro:Secondary/Unknown ds:UpToDate/DUnknown r----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
How can I tell DRBD to reconnect the ressource on boot?
Starting:
drbdadm connect drbd-sr1
is working fine and the resync starts.
I inserted the logfile and the config on the buttom of the mail.
Thank you for your help
Phil
global { usage-count yes; }
common {
protocol C;
net {
allow-two-primaries;
after-sb-0pri discard-zero-changes;
after-sb-1pri consensus;
after-sb-2pri disconnect;
}
disk {
max-bio-bvecs 1;
}
startup {
#become-primary-on both;
}
handlers {
split-brain "/usr/lib/drbd/notify-split-brain.sh";
}
syncer { rate 80M; }
}
resource drbd-sr1 {
device /dev/drbd1;
disk /dev/md0;
meta-disk internal;
on xenpool11{
address 172.16.12.111:7788;
}
on xenpool12{
address 172.16.12.112:7788;
}
}
Apr 7 16:15:04 xenpool12 kernel: drbd: initialized. Version: 8.3.7
(api:88/proto:86-91)
Apr 7 16:15:04 xenpool12 kernel: drbd: GIT-hash:
ea9e28dbff98e331a62bcbcc63a6135808fe2917 build by
[email protected], 2010-02-08 12:20:27
Apr 7 16:15:04 xenpool12 kernel: drbd: registered as block device
major 147
Apr 7 16:15:04 xenpool12 kernel: drbd: minor_table @ 0xeec3ed40
Apr 7 16:15:04 xenpool12 kernel: block drbd1: Starting worker thread
(from cqueue/0 [5727])
Apr 7 16:15:04 xenpool12 kernel: block drbd1: disk( Diskless ->
Attaching )
Apr 7 16:15:04 xenpool12 kernel: block drbd1: Found 4 transactions
(192 active extents) in activity log.
Apr 7 16:15:04 xenpool12 kernel: block drbd1: Method to ensure write
ordering: barrier
Apr 7 16:15:04 xenpool12 kernel: block drbd1: Backing device's
merge_bvec_fn() = f04701b0
Apr 7 16:15:04 xenpool12 kernel: block drbd1: max_segment_size ( =
BIO size ) = 4096
Apr 7 16:15:04 xenpool12 kernel: block drbd1: Adjusting my ra_pages
to backing device's (32 -> 64)
Apr 7 16:15:04 xenpool12 kernel: block drbd1: drbd_bm_resize called
with capacity == 3906930672
Apr 7 16:15:04 xenpool12 kernel: block drbd1: resync bitmap:
bits=488366334 words=15261448
Apr 7 16:15:04 xenpool12 kernel: block drbd1: size = 1863 GB
(1953465336 KB)
Apr 7 16:15:05 xenpool12 kernel: block drbd1: recounting of set bits
took additional 9 jiffies
Apr 7 16:15:05 xenpool12 kernel: block drbd1: 0 KB (0 bits) marked
out-of-sync by on disk bit-map.
Apr 7 16:15:05 xenpool12 kernel: block drbd1: disk( Attaching ->
UpToDate )
Apr 7 16:15:05 xenpool12 kernel: block drbd1: Barriers not supported
on meta data device - disabling
Apr 7 16:15:05 xenpool12 kernel: block drbd1: conn( StandAlone ->
Unconnected )
Apr 7 16:15:05 xenpool12 kernel: block drbd1: Starting receiver
thread (from drbd1_worker [5734])
Apr 7 16:15:05 xenpool12 kernel: block drbd1: receiver (re)started
Apr 7 16:15:05 xenpool12 kernel: block drbd1: conn( Unconnected ->
WFConnection )
Apr 7 16:15:05 xenpool12 kernel: block drbd1: bind before connect
failed, err = -99
Apr 7 16:15:05 xenpool12 kernel: block drbd1: conn( WFConnection ->
Disconnecting )
Apr 7 16:15:05 xenpool12 kernel: block drbd1: Discarding network
configuration.
Apr 7 16:15:05 xenpool12 kernel: block drbd1: Connection closed
Apr 7 16:15:05 xenpool12 kernel: block drbd1: conn( Disconnecting ->
StandAlone )
Apr 7 16:15:05 xenpool12 kernel: block drbd1: receiver terminated
Apr 7 16:15:05 xenpool12 kernel: block drbd1: Terminating receiver
thread
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
