Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Cc: "Montrose, Ernest" <Ernest.Montrose@stratus.com>
Subject: Re: [Drbd-dev] DRBD8: Stuck in WFBitMapS state even across reboot.
Date: Thu, 30 Nov 2006 16:11:40 +0100	[thread overview]
Message-ID: <200611301611.41232.philipp.reisner@linbit.com> (raw)
In-Reply-To: <BD7042533C2F8943A6A4257A9E31C45439C843@EXNA.corp.stratus.com>

Am Montag, 27. November 2006 23:28 schrieb Montrose, Ernest:
> Hi all,
> I am seeing a problem where both nodes get stuck in the WFBitMaps state
> even across a reboot.
> Dmesg also reveals this on both nodes:
> Drbd0: [drbd0_receiver/4800] sock_sendmsg time expired, ko = 4294967256
> .......
> Drbd0: Split-brain detected, manuall solved. Sync from this node
> Both nodes reports this split brain message.  My configuration for
> device 0 has the following new
> Settings NET:
> rr-conflict violently;
> after-sb-1pri violently-as0p;
> after-sb-2pri violently-as0p;
>
> Thanks for any help.
>

Hi Ernest,

Could you please give us a better description, how we can reproduce this
here ?

-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-11-30 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-27 22:28 [Drbd-dev] DRBD8: Stuck in WFBitMapS state even across reboot Montrose, Ernest
2006-11-30 15:11 ` Philipp Reisner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-30 15:38 Montrose, Ernest
2006-11-30 19:59 ` Lars Ellenberg
2006-12-01  9:43   ` Philipp Reisner
2006-11-30 20:12 Montrose, Ernest
2006-12-01 12:06 Montrose, Ernest

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=200611301611.41232.philipp.reisner@linbit.com \
    --to=philipp.reisner@linbit.com \
    --cc=Ernest.Montrose@stratus.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