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] DRBD8: The last few changes appears to have broken St state machine.
Date: Fri, 27 Oct 2006 11:04:28 +0200	[thread overview]
Message-ID: <200610271104.28514.philipp.reisner@linbit.com> (raw)
In-Reply-To: <BD7042533C2F8943A6A4257A9E31C45439C817@EXNA.corp.stratus.com>

Am Mittwoch, 25. Oktober 2006 21:33 schrieb Montrose, Ernest:
> Hi all:
> I am using the same configuration I have always used. With the latest
> changes (I would say a couple of days worth but don't quote me).
> A look at /proc/drbd on Node 1 yields:
> St: Secondary/Primary
> A look at /proc/drbd on Node 2 yields:
> St: Secondary/Secondary <----- Which is not true.
>
> I go on node 2 and try to set it to Primary, since node 1 thinks it is
> anyway:
> # drbdadm primary shared.fs
> **Thinks about it for a few*** then get:
> No response from the DRBD driver! Is the module loaded?
> Error code 102200106 unknown.
> You should update the drbd userland tools.
> Command 'drbdsetup /dev/drbd15 primary' teminated with exit code 20
> Drbdadm aborting.
>
> Puts in older driver, reboot and all is fine now....
>

Oops!

Just fixed in SVN. 

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

      reply	other threads:[~2006-10-27  9:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 19:33 [Drbd-dev] DRBD8: The last few changes appears to have broken St state machine Montrose, Ernest
2006-10-27  9:04 ` 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=200610271104.28514.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