On Wed, Mar 20, 2019 at 07:31:02PM +0100, Valentin Vidic wrote: > Right, but I'm not sure how this would help in the above situation > unless the DRBD can undo the local write that did not succeed on the > peer?
Ah, it seems the activity log handles the undo by storing the location of these dirty blocks (not replicated properly): https://docs.linbit.com/docs/users-guide-8.4/#s-activity-log So on resync these blocks would get copied from the new primary. -- Valentin _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/