Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I have an active/active drbd config with a pair of resources on two
servers and I'm busy figuring out how it all works. One issue that I've
come up with as part of it's integration into heartbeat, is that 'drbdisk
resource start' will promote an Incosistent Secondary to Primary while it
is a SyncTarget. While I'm confident that if my hearbeat configuration is
correct and that I, the operator, don't tell it to do something dumb that
this wouldn't come up but it seems like a really bad idea to let this
happen. What am I missing from the drbd config? Appologies if this is
obvious.
# cat /proc/drbd
version: 8.0.6 (api:86/proto:86)
SVN Revision: 3048 build by root at a.store, 2007-09-10 15:25:56
0: cs:SyncTarget st:Secondary/Secondary ds:Inconsistent/UpToDate C r---
ns:24 nr:1391984176 dw:1391970792 dr:1575 al:0 bm:85165 lo:421 pe:2108 ua:419 ap:0
[============>.......] sync'ed: 64.9% (737752/2097087)M
finish: 8:02:37 speed: 26,080 (29,040) K/sec
resync: used:6/31 hits:86915009 misses:84964 starving:0 dirty:0 changed:84964
act_log: used:0/127 hits:6 misses:0 starving:0 dirty:0 changed:0
...
# drbdadm primary r0
Child process does not terminate!
Exiting.
(What about that error? running 'drbdsetup /dev/drbd0 primary' works
fine -- is there a way to adjust the alarm or is something else up?)
# cat /proc/drbd
version: 8.0.6 (api:86/proto:86)
SVN Revision: 3048 build by root at a.store, 2007-09-10 15:25:56
0: cs:SyncTarget st:Primary/Secondary ds:Inconsistent/UpToDate C r---
ns:24 nr:1396417296 dw:1396401864 dr:1575 al:0 bm:85432 lo:485 pe:1707 ua:483 ap:0
[=============>......] sync'ed: 65.1% (733425/2097087)M
finish: 8:12:48 speed: 25,368 (29,040) K/sec
resync: used:6/31 hits:87191344 misses:85234 starving:0 dirty:0 changed:85234
act_log: used:0/127 hits:6 misses:0 starving:0 dirty:0 changed:0
...
# cat /etc/drbd.conf
global {
usage-count yes;
}
common {
syncer { rate 500M; }
}
resource r0 {
protocol C;
disk {
on-io-error detach;
}
syncer {
rate 500M;
# after "r0";
}
net {
cram-hmac-alg "sha1";
shared-secret "blah";
#this may increase performance?
max-buffers 4096;
max-epoch-size 1024;
}
on a.store {
device /dev/drbd0;
disk /dev/sda;
address 192.168.1.1:7788;
meta-disk internal;
}
on b.store {
device /dev/drbd0;
disk /dev/sda;
address 196.168.1.2:7788;
meta-disk internal;
}
}
...
--
Kelsey Cummings - kgc at corp.sonic.net sonic.net, inc.
System Architect 2260 Apollo Way
707.522.1000 Santa Rosa, CA 95407