[DRBD-user] invalidate-remote does not work in StandAlone mode

Felix Frank ff at mpexnet.de
Thu Aug 4 12:39:41 CEST 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 08/04/2011 12:33 PM, Mark wrote:
> I'm getting:
> drbdsetup 0 invalidate-remote
> 0: State change failed: (-6) Refusing to be Outdated while Connected

huh, that's misleading.

> Can we fix that? I'm starting with a peerless configuration and the AL
> updates are hurting performance without reason.

In standalone, the AL isn't your only concern, there's also a quicksync
bitmap that gets constantly updated (although that should be cheap).

What are you trying to do? invalidate-remote doesn't make any sense
while there's not peer you can invalidate. Even if there was, all you'd
"gain" would be a mandatory full sync taking place on top of your AL woes.

Have you tweaked your al-extents setting?

Have you tested whether operation with a peer is indeed slower?

Have you compared Standalone DRBD performance with performance when not
using DRBD at all?


More information about the drbd-user mailing list