[DRBD-user] FAQ: Reconnecting after a temporary primary node failure

Mauricio Tavares raubvogel at gmail.com
Tue Mar 8 15:02:42 CET 2011

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


On Tue, Mar 8, 2011 at 8:47 AM, Felix Frank <ff at mpexnet.de> wrote:
>
>> I feel like I must be missing something obvious here but can't figure
>> out what...
>
> I didn't notice anything obvious to me. Before you try and reconnect,
> examine the UUIDs on both sides using drbdadm get-gi.
> The second block on the Primary should be equal to the first one on the
> Secondary. It shouldn't split-brain then.
>
      Oh. When you say reconnect do you mean reconnecting ethernet or
drdbadm reconnect? If the former, too late and I will have to do it
all again. If the latter, I have not done it yet so I should be good.
In any case, here is the output with db1's ethernet cable reconnected:

root at db1:~# drbdadm get-gi r0
3F197C90A31FC957:AD47F2C0FCB0CE1B:D8335248BF8F073F:201C5D8F032E15FB:1:1:1:0:0:0:0
root at db1:~#

root at db2:~# drbdadm get-gi r0
AD47F2C0FCB0CE1A:0000000000000000:D8335248BF8F073E:201C5D8F032E15FB:1:1:0:0:0:0:0
root at db2:~#

So, from what you said, I *should* have

AD47F2C0FCB0CE1B
AD47F2C0FCB0CE1A

the same, but as you can see the last character is different. Loads of fun.

> HTH,
> Felix
>



More information about the drbd-user mailing list