Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
As a longtime user of drbd versions 0.5.6 through 0.7.22 I thought I
wouldn't have much of a problem setting up 8.0 on a new cluster.
Wrong.
Mostly I think that I'm running into a lack of documentation, and thus
making stupid mistakes in setup.
Desired config: two drbd devices on software raid with internal metadata
for use inprimary/secondary config.
* Info that meta data needs to be created as a seperate step is fairly
sparse.
* startup script for gentoo is somewhat minimalistic- any special reason
the script does _not_ load the drbd module?
So far I've created the md devices I want to run drbd on, and created
drbd meta data on the devices.
Kernel is 2.6.19
Trying to start drbd results in an error:
* Starting DRBD ...
Failure: (115) Meta device is already mounted.
Command '/sbin/drbdsetup /dev/drbd0 disk /dev/md3 /dev/md3 flexible
--set-defaults --create-device --on-io-error=detach' terminated with
exit code 10
There is nothing obvious that's accessing/using /dev/md3 - no lvm, no dm
modules, not mounted.
Any hints what I'm doing wrong are greatly apreciated.
Thanks, Martin
Config file:
-------------------------
global {
usage-count yes;
}
common {
protocol C;
syncer {
rate 100M;
al-extents 257;
}
handlers {
pri-on-incon-degr "echo O > /proc/sysrq-trigger ; halt -f";
pri-lost-after-sb "echo O > /proc/sysrq-trigger ; halt -f";
local-io-error "echo O > /proc/sysrq-trigger ; halt -f";
outdate-peer "/usr/sbin/drbd-peer-outdater";
}
startup {
wfc-timeout 300;
degr-wfc-timeout 120; # 2 minutes.
}
disk {
on-io-error detach;
}
net {
timeout 60; # 6 seconds (unit = 0.1 seconds)
connect-int 10; # 10 seconds (unit = 1 second)
ping-int 10; # 10 seconds (unit = 1 second)
ping-timeout 5; # 500 ms (unit = 0.1 seconds)
ko-count 4;
allow-two-primaries;
cram-hmac-alg "sha1";
shared-secret
"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
x";
after-sb-0pri disconnect;
after-sb-1pri disconnect;
after-sb-2pri disconnect;
rr-conflict disconnect;
}
}
resource drbd0 {
on webc-neu1 {
device /dev/drbd0;
disk /dev/md3;
address 192.168.0.21:7788;
flexible-meta-disk internal;
}
on webc-neu2 {
device /dev/drbd0;
disk /dev/md3;
address 192.168.0.23:7788;
flexible-meta-disk internal;
}
}
resource drbd1 {
syncer {
after "drbd0";
}
on webc-neu1 {
device /dev/drbd1;
disk /dev/md4;
address 192.168.0.21:7789;
flexible-meta-disk internal;
}
on webc-neu2 {
device /dev/drbd1;
disk /dev/md4;
address 192.168.0.23:7789;
flexible-meta-disk internal;
}
}