Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] RE: [DRBD-cvs] svn commit by phil - r2607 - trunk/drbd - The fix forthe "both nodes in WFBitMaps" issue, Ernest
Date: Thu, 21 Dec 2006 09:38:53 +0100	[thread overview]
Message-ID: <200612210938.53959.philipp.reisner@linbit.com> (raw)
In-Reply-To: <BD7042533C2F8943A6A4257A9E31C45439C897@EXNA.corp.stratus.com>

Am Mittwoch, 20. Dezember 2006 18:46 schrieb Montrose, Ernest:
> Hi Phil,
> I am still seeing this issue that I reported a while back and for which
> you submitted a fix (see original message below).  But essentially after
> the drbd heartbeat link is disconnected and Split brain occurred, both
> nodes thinks they should be the sync source.  They send their peers(each
> other) to the following states:
> peer( Unknown -> Secondary ) conn( WFReportParams -> WFBitMapS ) pdsk(
> DUnknown -> UpToDate ) At the same time..
> This state persists across a reboot and the drbd_receiver thread loops
> on both nodes with:
>


Hi Ernest,

Could you please post the kernel messages from both nodes including
the disconnect time, as well the reconnect time ?

And a "drbdadm show-gi" on both nodes from the resource in question
would be helpfull as well.

Thanks!

-Phil
-- 
: Dipl-Ing Philipp Reisner                      Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH          Fax +43-1-8178292-82 :
: Vivenotgasse 48, 1120 Vienna, Austria        http://www.linbit.com :

      reply	other threads:[~2006-12-21  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 17:46 [Drbd-dev] RE: [DRBD-cvs] svn commit by phil - r2607 - trunk/drbd - The fix forthe "both nodes in WFBitMaps" issue, Ernest Montrose, Ernest
2006-12-21  8:38 ` Philipp Reisner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200612210938.53959.philipp.reisner@linbit.com \
    --to=philipp.reisner@linbit.com \
    --cc=drbd-dev@lists.linbit.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox