Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
When starting a new DRBD setup, I'm getting the following when starting
up the service:
Starting DRBD resources: [ d(media) drbd1: No usable activity log found.
drbd1: meta data flush failed with status -95, disabling md-flushes
s(media) n(media) ].
When using drbdadm to set the first node as primary, I get:
> drbdadm -- --overwrite-data-of-peer primary media
drbd1: Forced to consider local data as UpToDate!
Here's my config - am I doing something wrong? This same config's
working on identical servers with no problem.
resource media {
protocol C;
handlers {
pri-on-incon-degr "echo 'DRBD: primary requested but inconsistent!'
| wall; /etc/init.d/heartbeat stop"; #"halt -f";
pri-lost-after-sb "echo 'DRBD: primary requested but lost!' | wall;
/etc/init.d/heartbeat stop"; #"halt -f";
}
startup {
degr-wfc-timeout 120; # 2 minutes.
wfc-timeout 120; # 2 minutes.
}
disk {
on-io-error detach;
}
net {
timeout 120;
connect-int 20;
ping-int 20;
max-buffers 2048;
max-epoch-size 2048;
ko-count 30;
cram-hmac-alg "sha1";
shared-secret "XXXXXX";
after-sb-0pri disconnect;
after-sb-1pri disconnect;
after-sb-2pri disconnect;
}
syncer {
rate 30M;
al-extents 503;
verify-alg sha1;
}
on SERVER1 {
device /dev/drbd1;
disk /dev/xvda4;
address 172.16.1.5:7789;
meta-disk internal;
}
on SERVER2 {
device /dev/drbd1;
disk /dev/xvda4;
address 172.16.1.6:7789;
meta-disk internal;
}
}
Thanks!
Mike Sweetser