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] DRBD-8: attach seems to be broken
Date: Fri, 15 Sep 2006 12:18:56 +0200	[thread overview]
Message-ID: <200609151218.56673.philipp.reisner@linbit.com> (raw)
In-Reply-To: <342BAC0A5467384983B586A6B0B37671038B06E2@EXNA.corp.stratus.com>

Am Donnerstag, 14. September 2006 17:24 schrieb Graham, Simon:
> I'm not running the absolute latest but some change in the past day
> seems to have broken attach after detach - the state goes to Attaching
> and never transitions to UpToDate. I haven't been able to figure out how
> the side doing the attach is actually supposed to transition - it's
> somewhere in receive_state() I think but it eludes me for the moment. I
> can see that on the other side, receipt of ReportState when the peer
> says it's disk state is Attaching causes it to send ReportState in reply
> which the comments says causes the peer to promote from
> Attaching->UpToDate but I cant see how that actually happens...
>
> At the moment, I'm using revision 2423 which is just one back from the
> tip and looking at the diffs for that, I don't see anything that would
> fix this issue.
>
> Any suggestions?

Hi Simon,

Thanks for pointing this out!

I fixed it with this commit:
http://lists.linbit.com/pipermail/drbd-cvs/2006-September/001238.html

-Philipp
-- 
: 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-09-15 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14 15:24 [Drbd-dev] DRBD-8: attach seems to be broken Graham, Simon
2006-09-15 10:18 ` 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=200609151218.56673.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