[DRBD-user] Avoiding data inconsistencies after a split-brain

Lars Ellenberg lars.ellenberg at linbit.com
Fri Apr 16 21:38:50 CEST 2010

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, Apr 16, 2010 at 02:02:22PM -0300, Andre Nathan wrote:
> Hello
> I'm setting up a two-node active/active cluster with DRBD and OCFS2.
> When the nodes lose communication with one another, a split-brain
> happens, and both machines and up in the stand-alone/active state.
> One possible solution to minimize the amount of time where writes can be
> done to both nodes without synchronization would be to remount the
> filesystems as read-only with the split-brain hook. This, however, won't
> avoid inconsistencies with writes happening before the hook has a chance
> to run.

disk {
	fencing resource-and-stonith;
	# this mode implicitly freezes IO and only resumes IO if peer is
	# successfully fenced as reported by the fence peer script.
	# Or if the admin explicitly resumes io.
handler {
	fence-peer "some script that kills the other node";

: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
please don't Cc me, but send to list   --   I'm subscribed

More information about the drbd-user mailing list