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: ASSERT( mdev->bc->md.uuid[Bitmap] == 0 ) in drbd_main.c:drbd_uuid_new_current()
Date: Wed, 1 Aug 2007 17:07:50 +0200	[thread overview]
Message-ID: <200708011707.51055.philipp.reisner@linbit.com> (raw)
In-Reply-To: <BD7042533C2F8943A6A4257A9E31C454F4799D@EXNA.corp.stratus.com>

On Tuesday 31 July 2007 23:18:05 Montrose, Ernest wrote:
> Hi all,
> We are seeing another problem that occurs with the following sequence of
> events:
> drbdadm secondary vm2.root.fs
> drbdadm detach vm2.root.fs
> drbdadm primary vm2.root.fs
> drbdadm secondary vm2.root.fs
> drbdadm primary vm2.root.fs <----- This causes the assert
> drbdadm attach vm2.root.fs  <------ This causes an instant Split brain
> but only because of the assert above.
>
> I think what's happening is that we are generating a new bitmap UUID
> every time the diskless peer goes Primary.
> I see no reason why we have to do this more then once.  I include a tiny
> patch to do it just one time.
>

You are absolutely right.

http://lists.linbit.com/pipermail/drbd-cvs/2007-August/001612.html

-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:[~2007-08-01 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 21:18 [Drbd-dev] DRBD8: ASSERT( mdev->bc->md.uuid[Bitmap] == 0 ) in drbd_main.c:drbd_uuid_new_current() Montrose, Ernest
2007-08-01 15:07 ` 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=200708011707.51055.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