<div dir="ltr">Thanks, that's very useful feedback. It took me quite some time to recover from this split-brain condition - none of the recipes I found online would quite work. In fact, I am not entirely sure I know exactly what it was that sorted it out for me, in the end :-( </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 4, 2019 at 4:33 PM Adam Goryachev <<a href="mailto:mailinglists@websitemanagers.com.au">mailinglists@websitemanagers.com.au</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 5/4/19 5:09 am, JCA wrote:<br>
> I believe that you are right in your assessment. Unfortunately, after <br>
> this I seem to be stuck in a situation in which both nodes are not <br>
> connected through DRBD:<br>
><br>
> In A:<br>
><br>
> # cat /proc/drbd<br>
> version: 8.4.11-1 (api:1/proto:86-101)<br>
> GIT-hash: 66145a308421e9c124ec391a7848ac20203bb03c build by <br>
> mockbuild@, 2018-11-03 01:26:55<br>
><br>
> 1: cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown C r-----<br>
> ns:0 nr:0 dw:4 dr:2161 al:1 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:336<br>
><br>
> # drbdadm status<br>
> my-data role:Primary<br>
> disk:UpToDate<br>
> peer connection:Connecting<br>
><br>
> In B:<br>
><br>
> # cat /proc/drbd<br>
> version: 8.4.11-1 (api:1/proto:86-101)<br>
> GIT-hash: 66145a308421e9c124ec391a7848ac20203bb03c build by <br>
> mockbuild@, 2018-11-03 01:26:55<br>
><br>
> 1: cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown C r-----<br>
> ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:24<br>
><br>
> # drbdadm status<br>
> my-data role:Secondary<br>
> disk:UpToDate<br>
> peer connection:Connecting<br>
><br>
> I have tried numerous things - including rebooting both VMs where the <br>
> nodes live - to no avail.<br>
<br>
Sounds like both sides have been a primary and so now they both think <br>
the other is out of date (ie, split brain). What you will need to do is <br>
tell DRBD which one should discard it's data and become secondary, you <br>
can then reconnect them and DRBD will re-copy the data, re-sync, and get <br>
back into a working state.<br>
<br>
This is a good lesson to work out why you ended up with a split brain <br>
situation it sounds like:<br>
<br>
1. server A was up while server B was down<br>
<br>
2. server A went down, and then server B came up<br>
<br>
3. server A then came up without any valid network connection to server B<br>
<br>
or, you have a non-standard or incorrect config. DRBD (in my experience) <br>
would notice, catch, and prevent you from getting into this situation.<br>
<br>
You should also refer to your log files, they will contain lots of <br>
useful information, as well as details that you should post to the list <br>
so we can see what mess you have created....<br>
<br>
Hope it helps..<br>
<br>
Regards,<br>
Adam<br>
<br>
-- <br>
Adam Goryachev Website Managers <a href="http://www.websitemanagers.com.au" rel="noreferrer" target="_blank">www.websitemanagers.com.au</a><br>
<br>
-- <br>
The information in this e-mail is confidential and may be legally privileged.<br>
It is intended solely for the addressee. Access to this e-mail by anyone else<br>
is unauthorised. If you are not the intended recipient, any disclosure,<br>
copying, distribution or any action taken or omitted to be taken in reliance<br>
on it, is prohibited and may be unlawful. If you have received this message<br>
in error, please notify us immediately. Please also destroy and delete the<br>
message from your computer. Viruses - Any loss/damage incurred by receiving<br>
this email is not the sender's responsibility.<br>
_______________________________________________<br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com" target="_blank">drbd-user@lists.linbit.com</a><br>
<a href="http://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br>
</blockquote></div>