Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello, following instructions detailed at
http://www.howtoforge.com/high_availability_nfs_drbd_heartbeat_p3
but instead installing from Debian repository, installing 0.7.18 from
tarball, when running drbdadm -- connect all on primary server, we lost the
connection and even no ping response was received.
Secondary /proc/drbd shows this after crash:
version: 0.7.18 (api:78/proto:74)
SVN Revision: 2176 build by root at ramona.ran.es, 2006-05-03 12:56:02
0: cs:StandAlone st:Secondary/Unknown ld:Consistent
ns:52724 nr:0 dw:0 dr:52724 al:0 bm:3 lo:0 pe:0 ua:0 ap:0
1: cs:Unconfigured
On primary server, the command sequence was:
modprobe drbd (ran on both machines)
drbdadm up all (ran on both machines)
cat /proc/drbd
version: 0.7.18 (api:78/proto:74)
SVN Revision: 2176 build by root at raimunda, 2006-05-03 12:54:34
0: cs:SyncTarget st:Secondary/Secondary ld:Inconsistent
ns:0 nr:13788 dw:13788 dr:0 al:0 bm:0 lo:0 pe:25 ua:0 ap:0
[>...................] sync'ed: 0.1% (63165/63179)M
finish: 20:43:52 speed: 840 (860) K/sec
1: cs:Unconfigured
drbdadm -- --do-what-I-say primary all
drbdadm -- connect all
(this command does not returned to bash)
DRBD Version: 0.7.18
Kernel Version: Debian sarge 2.6.8-3
Connected throught vtun link with zlib compression
Config file:
resource r0 {
protocol C;
incon-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ; sleep 60 ;
halt -f";
startup {
}
disk {
on-io-error detach;
}
net {
}
syncer {
rate 1M;
group 1;
al-extents 257;
}
on raimunda {
device /dev/drbd0;
disk /dev/hda4;
address 10.3.0.2:7788;
meta-disk internal;
}
on ramona.ran.es {
device /dev/drbd0;
disk /dev/hda6;
address 10.3.0.1:7788;
meta-disk internal;
}
}