Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi, After testing a shutdown of the primary DRBD, the secondary took over alright, but then when the primary come back, I got the following on the secondary: secondary:~# /etc/init.d/drbd start Starting DRBD resources: [ n0 ]. Command '/bin/bash -c IP=10.0.0.10; IPQ=${IP//./\\.};peerIP=10.0.0.13; peerIPQ=${peerIP//./\\.};LANG=; PATH=/sbin/:$PATH;if type -p ip ; then ip -o route get to $peerIP from $IP 2>/dev/null | grep -qE ^$peerIPQ' from '$IPQ' ';fi >/dev/null drbdadm:verify_ips' terminated with exit code 1 /etc/drbd.conf:220: in resource r0: No route from me (10.0.0.10) to peer (10.0.0.13). *************************************************************** DRBD's startup script waits for the peer node(s) to appear. - In case this node was already a degraded cluster before the reboot the timeout is 120 seconds. [degr-wfc-timeout] - If the peer was available before the reboot the timeout will expire after 10 seconds. [wfc-timeout] (These values are for resource 'r0'; 0 sec -> wait forever) To abort waiting enter 'yes' [11]: To abort waiting enter 'yes' [ -- ]: secondary:~# cat /proc/drbd version: 0.7.10 (api:77/proto:74) SVN Revision: 1743 build by root at castor, 2005-10-28 16:28:10 0: cs:WFConnection st:Secondary/Unknown ld:Consistent ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 primary:~# cat /proc/drbd version: 0.7.10 (api:77/proto:74) SVN Revision: 1743 build by root at castor, 2005-10-28 16:28:10 0: cs:WFConnection st:Secondary/Unknown ld:Consistent ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 # uname -a Linux mercury 2.6.14-drdb-1 I use from Debian Stable: ii drbd0.7-module-source 0.7.10-3 Secondary can ping primary alright (and vice-versa). What'a wrong? Thanks, Yann -- Network & System Engineer Goelaan SA, Switzerland Tel. +41-22-960 98 20 Fax +41-22-960 98 21 http://www.goelaan.ch