Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi ! Like many other (well, at least since the last two weeks since I've been following the list .. <grin>) I am also very interested in the 0.8 brance due to its primary/primary role ability. I have succesfully tested with GFS and OCFS2. Both seem te be working just fine ... Doing a bonnie++ on both nodes at the same time (but in different subdirectory's on the drbd0) seems to work without any problem. But ..... rebooting a node while the other stays active ... or faking it's crash tends to lead upto a split brain as others have noticed. Even if the 'broken one' has done nothing on its disks. Most of the times only a full re-sync seemed to work. I have not tried the "drbdadm -- --discard-my-data connect all" though, will do that at once ! Would it be very hard to indeed 'detect' a broken (or rebooted) node and let it catch-up with the running available primary? Yours, Christiaan den Besten ----- Original Message ----- From: Igor Morgado To: drbd-user at linbit.com Sent: Thursday, August 17, 2006 3:28 PM Subject: Re: [DRBD-user] Re: DRBDv8 + LVM (problems in cstate)(LONG) when I first met the problem I have tried to "invalidate" one node to make the connection work. But that dont solved the problem. and yes. your solution solved the problem. Thank you for all patience and help. On 8/17/06, Lars Ellenberg <Lars.Ellenberg at linbit.com> wrote: / 2006-08-16 16:59:29 -0300 \ Igor Morgado: > the kern.log (im on debian) it says more.. > > Aug 16 16:22:09 magratea kernel: drbd0: conn( WFConnection -> WFReportParams ) > Aug 16 16:22:09 magratea kernel: drbd0: Handshake successful: DRBD Network Protocol version 82 > Aug 16 16:22:09 magratea kernel: drbd0: Split-Brain detected, dropping connection! there you are. that is the reason. > Aug 16 16:22:09 magratea kernel: drbd0: conn( WFReportParams -> StandAlone ) > > magratea:/# drbdadm get-gi all > 5A114EE2F3E64BC3:7BED9741D8E63232:D9D7884582F7EA10:73F91785A227EB8E:1:1:0:0:0:0 > > cricket:/# drbdadm get-gi all > 350557AFB917FE33:7BED9741D8E63233:D9D7884582F7EA11:73F91785A227EB8F:0:0:0:0:0:0 first uuid differs, other (bitmap, history) uuids are identical: data set has been modified independently, split-brain detected... to resolv this, you have to tell drbd which of the independen modifications of the data set you want to discard. to do so: cricket# drbdadm -- --discard-my-data connect all magratea# drbdadm connect all should do the trick. now, we probably should be able to auto-resolv this if one side is "inconsistent", as is aparently the case here. -- : Lars Ellenberg Tel +43-1-8178292-0 : : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 : : Schoenbrunner Str. 244, A-1120 Vienna/Europe http://www.linbit.com : __ please use the "List-Reply" function of your email client. _______________________________________________ drbd-user mailing list drbd-user at lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user ------------------------------------------------------------------------------ _______________________________________________ drbd-user mailing list drbd-user at lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20060818/80ca53de/attachment.htm>