Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Dear list's friends, I've noticed one strange action on two nodes with the
following listed drbd.conf setup.
The two nodes are crossover connected with two bonded nics, set for high
availability, not for performances.
For some reason, at the startup the bonded drbd network didn't came up
correctly (could be for the crossover connection? Forget it, it is not the
issue I'll talk about)), so it was not possible to ping 10.1.1.x each other,
no connection for drbd.
The supposed scenario I expected to be WFConnection on both nodes, and it
was, but with Primary/Unknown on the server-1 and Secondary/Unknown on the
server-2.
My issue is that they both were Secondary and I had to manually issue the
"drbdadm primary" command on server-1.
It did work, not a big deal, but it would be better if this can work as
expected.
Could be due to some settings in the drbd.conf?
What follow is the drbd.con content and I thank you in advance for any kind
of tip.
Robert
_________________________________________
---- drbd.conf ----
global {
usage-count yes;
}
common {
syncer {
rate 50M;
verify-alg md5;
csums-alg md5;
}
}
# single sata is 80MB/sec, may be is better to set half of the speed
resource drbd0 {
protocol C;
startup {
become-primary-on xenserver-1;
}
net {
cram-hmac-alg md5;
shared-secret "pwdpwd";
sndbuf-size 0;
rcvbuf-size 0;
data-integrity-alg md5;
}
disk {
max-bio-bvecs 1;
on-io-error detach;
no-disk-flushes;
}
on xenserver-1 {
device /dev/drbd0;
disk /dev/sdb;
address 10.1.1.1:7789;
meta-disk internal;
}
on xenserver-2 {
device /dev/drbd0;
disk /dev/sdb;
address 10.1.1.2:7789;
meta-disk internal;
}
handlers {
# split-brain "/usr/lib/drbd/notify-split-brain.sh root";
}
}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20100908/e937b667/attachment.htm>