Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi, On 07/30/2012 10:06 PM, JAMES GIBBON wrote: > version: 8.3.7 (api:88/proto:86-91) > srcversion: EE47D8BF18AC166BE219757 > 0: cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown C r---- > ns:0 nr:0 dw:27568823 dr:156762105 al:309656 bm:309639 lo:0 pe:0 > ua:0 ap:0 ep:1 wo:b oos:10184632 > 1: cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown C r---- > ns:0 nr:0 dw:2451648 dr:14918745 al:1244 bm:1211 lo:0 pe:0 ua:0 ap:0 > ep:1 wo:b oos:1152564 > > And on the second, troublesome box: > > version: 8.3.7 (api:88/proto:86-91) > srcversion: EE47D8BF18AC166BE219757 > 0: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r---- > ns:0 nr:0 dw:0 dr:1705944 al:0 bm:107 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b > oos:954596 > 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r---- > ns:0 nr:0 dw:0 dr:1821288 al:0 bm:107 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b > oos:520192 > > > So it looks like at some level they aren't talking to each other > - I don't see the usual "UpToDate/UpToDate". you could say that ;) Judging from your log excerpt, there might be a connectivity issue, but this could very well be a pure split brain that needs resolving. See http://www.drbd.org/users-guide/s-resolve-split-brain.html and note that you will likely loose whatever has been written to your "troubled" node. You may want to copy precious data if any has been written. What we'd need to see is your drbd configuration. Also the connection states of both nodes' respective NICs. Finally: Have you tried just issuing "drbdadm connect all" on the second node? HTH, Felix