[DRBD-user] Consistent device to primary fences remote node

Federico Simoncelli federico.simoncelli at gmail.com
Tue Dec 2 10:53:56 CET 2008

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


On Fri, Nov 28, 2008 at 12:05 PM, Lars Ellenberg
<lars.ellenberg at linbit.com> wrote:
>> When you correctly shut down the server 2 the drbd service is cleanly
>> stopped. Running "drbdadm show-gi" shows that "Data was/is currently
>> up-to-date" is set to 0. This means that the resource is automatically
>> Outdated.
>
> is that so.
> hm.
> /me looks up the state handling code...
> right you are.
>
> if we are Connected, and a node voluntarily leaves the cluster,
> and a drbd fencing policy is configured, and the other node is Primary,
> then the leaving node is requested to outdate itself prior to disconnect.

Hi, thank you for your answer. Can you point this part in the code?
(file/function) Thanks.

>> I just can't boot a single primary if both nodes were incorrectly shut
>> down.
>
> or if you had a network hickup first.
> but, right, you get a fencing race on network hickup.
> nice.

I think this is a pretty common behaviour, isn't it?

Thank you.
-- 
Federico.



More information about the drbd-user mailing list