Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi,
We have a test DRBD setup running in active/passive. Node1 is the
primary and node2 is the secondary. Yesterday, we rebooted node2 and now
we have a status of WFReportParams/WFConnection showing on the primary
and secondary respectively. Can we recover from this? Any help would be
much appreciated - We don't have any in-house DRBD expertise.
I'm guessing we should have run something like "drbdadm down all" on the
secondary before rebooting? I've included output below that should give
more detail about the setup and current state
# lsb_release -a
LSB Version:
core-2.0-noarch:core-3.0-noarch:core-2.0-x86_64:core-3.0-x86_64:desktop-3.1-amd64:desktop-3.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch
Distributor ID: SUSE LINUX
Description: SUSE Linux Enterprise Server 10 (x86_64)
primary
=======
# cat /proc/drbd
version: 0.7.22 (api:79/proto:74)
SVN Revision: 2572 build by lmb at dale, 2006-10-25 18:17:21
0: cs:WFReportParams st:Primary/Unknown ld:Consistent
ns:213178037 nr:3271238 dw:216623891 dr:243061160 al:940678 bm:2910
lo:0 pe:0 ua:0 ap:0
secondary
=========
# cat /proc/drbd
version: 0.7.22 (api:79/proto:74)
SVN Revision: 2572 build by lmb at dale, 2006-10-25 18:17:21
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
uptime
11:33am up 23:47, 1 user, load average: 0.06, 0.01, 0.00
# cat /etc/drbd.conf
resource "drbddata" {
protocol C;
net {
max-buffers 2048;
}
syncer {
rate 500M;
}
on node1 {
device /dev/drbd0;
disk /dev/cciss/c0d1p1;
address x.x.x.1:7001;
meta-disk /dev/cciss/c0d0p7 [0];
}
on node2 {
device /dev/drbd0;
disk /dev/cciss/c0d1p1;
address x.x.x.2:7001;
meta-disk /dev/cciss/c0d0p7 [0];
Thanks,
John