Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi All,
I have a two-primaries setup with three devices (drbd{0,1,2}). After an
unexpected shutdown of node2, the following situation occured:
resource provided by drbd0 on node1 is:
0: cs:StandAlone st:Primary/Unknown ds:UpToDate/DUnknown r---
ns:0 nr:0 dw:14484 dr:1375443 al:0 bm:348 lo:0 pe:0 ua:0 ap:0
resync: used:0/7 hits:65701 misses:91 starving:0 dirty:0 changed:91
act_log: used:0/257 hits:3590 misses:0 starving:0 dirty:0 changed:0
on node2 it's:
0: cs:StandAlone st:Secondary/Unknown ds:Inconsistent/DUnknown r---
ns:0 nr:0 dw:0 dr:0 al:0 bm:257 lo:0 pe:0 ua:0 ap:0
resync: used:0/7 hits:0 misses:0 starving:0 dirty:0 changed:0
act_log: used:0/257 hits:0 misses:0 starving:0 dirty:0 changed:0
I would like to make node2 resync its data from node1, but after
connecting them, they fall back to standalone mode. I tried this on node2:
drbdsetup /dev/drbd0 net 10.0.0.11:7788 10.0.0.10:7788 C -D
but the problem remains after reinitiating the connection. Also strange is
that the kernel log of node1 writes:
drbd0: State change failed: Refusing to be Primary without at least one UpToDate disk
drbd0: state = { cs:StandAlone st:Primary/Unknown ds:UpToDate/DUnknown r--- }
drbd0: wanted = { cs:StandAlone st:Primary/Unknown ds:Outdated/DUnknown r--- }
drbd0: outdate-peer helper broken, returned 0
drbd0: receiver terminated
which I just cannot understand. As node1 _is_ primary and uptodate
according to the output of /proc/drbd.
Any ideas?
Thanks,
Balint