[DRBD-user] Diagnosing a Failed Resource

Dan Barker dbarker at visioncomm.net
Tue Jan 22 15:55:23 CET 2013

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

>>> However, I still have no idea what caused the failures.

A split brain is caused by writing to both members while they are disconnected. What in your environment caused that to occur is probably lost in logs a week gone. But, if your procedures always allow only one node (primary) to write to a resource, even if it’s disconnected, then split-brain won’t occur.

“nuke the whole thing” certainly worked. So would have following the doc to invalidate the secondary copy and then simply connect. There is an excellent chapter in the manual about split-brain.


From: drbd-user-bounces at lists.linbit.com [mailto:drbd-user-bounces at lists.linbit.com] On Behalf Of Eric
Sent: Monday, January 21, 2013 5:08 PM
To: drbd-user at lists.linbit.com
Subject: Re: [DRBD-user] Diagnosing a Failed Resource

I decided to nuke the whole thing and start over:

On both nodes, I...


However, I still have no idea what caused the failures.

Ideas? Suggestions?

Eric Pretorious
Truckee, CA

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20130122/f815a9d0/attachment.htm>

More information about the drbd-user mailing list