[DRBD-user] Question: how to avoid full resync

Eli Dorfman (Voltaire) dorfman.eli at gmail.com
Sun May 17 16:12:50 CEST 2009

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

Lars Ellenberg wrote:
> On Thu, May 14, 2009 at 04:45:44PM +0300, Eli Dorfman (Voltaire) wrote:
>> Lars Ellenberg wrote:
>>> On Wed, May 13, 2009 at 06:35:43PM +0300, Eli Dorfman (Voltaire) wrote:
>>>> Hi,
>>>> Assuming a setup of 2 nodes primary A and secondary B.
>>>> After primary node A reboot and B became primary, is there a way to avoid full resync
>>>> from B to A?
>>> Uhm, well, yes: just do nothing and let DRBD do its job ;)
>>> Bitmap based resync is the "normal" resync operation.
>> After A was rebooted and B had almost no changes - 
>> yet when A goes up again it seems that B (drbd) performs full resync.  
> what makes you think so?

That's what I see in /proc/drbd.
we have a partition of 20GB and from the link speed and the time till process is completed,
it seems that drbd performs full resync.

>> Is this correct?
> it would not be expected.

So what could be the reason for this full resync?

>> is it configurable?
> no.

More information about the drbd-user mailing list