[DRBD-user] Restarting DRBD after no-disk-flushes?
florian.haas at linbit.com
Thu Apr 16 20:43:35 CEST 2009
it's actually this one:
Author: Philipp Reisner <philipp.reisner at linbit.com>
Date: Thu Mar 12 15:44:54 2009 +0100
Sane resync after detach on primary
Up to now we forced a full resync after a detach on a primary node
happened (no matter if it is caused by an administrative command,
or by an IO error).
Nowadays there is actually no reason to treat this worse than a crash
of a primary node.
When a primary crashes, we apply the AL afterwards to the bitmap.
The same is sufficient after a forcefull detach.
This fix was included in 8.3.1.
On 04/16/2009 09:32 AM, Lars Ellenberg wrote:
> On Thu, Apr 16, 2009 at 07:21:29AM +0200, Raoul Bhatia [IPAX] wrote:
>> On 15.04.2009 09:47, Lars Ellenberg wrote:
>>> Beware of changing disk parameters on a node in Primary role, though,
>>> as that does a detach/attach sequence. And until very recently,
>>> we required a full resync after a detach on a Primary. Now we lessend
>>> that to a resync of the area covered by the activity log, which still
>>> can be "a lot".
>> to which versions do you refer when saying "very recently"?
> I don't know from the top of my head, or I had been specific.
> check the changelog or git log.
: Florian G. Haas
: LINBIT Information Technologies GmbH
: Vivenotgasse 48, A-1120 Vienna, Austria
When replying, there is no need to CC my personal address.
I monitor the list on a daily basis. Thank you.
LINBIT® and DRBD® are registered trademarks of LINBIT.
More information about the drbd-user