From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Cc: "Montrose, Ernest" <Ernest.Montrose@stratus.com>
Subject: Re: [Drbd-dev] Cstate stays in "Disconnecting" after Heartbeat link down and up
Date: Fri, 6 Oct 2006 15:18:35 +0200 [thread overview]
Message-ID: <200610061518.35416.philipp.reisner@linbit.com> (raw)
In-Reply-To: <BD7042533C2F8943A6A4257A9E31C45439C7F6@EXNA.corp.stratus.com>
Am Donnerstag, 5. Oktober 2006 23:37 schrieb Montrose, Ernest:
> Hi all,
> If I do an ifdown and an ifup on the heartbeat link drbd goes into
> CS:Disconnecting . I cannot manually recover until a reboot. Should the
> state be "StandAlone" instead? I include a patch that seems to work for
> me.
>
Hi Ernest,
You patch did not fix the root case of the problem. The source of the
problem was the missing dec_net() in drbd_try_connect().
That lead to the receiver thread hang in
wait_event( ...,atomic_read(&mdev->net_cnt) == 0 ) in drbd_disconnect() .
Therefore the receiver thread did not terminate and could not set
the state finally to StandAlone.
see http://lists.linbit.com/pipermail/drbd-cvs/2006-October/001306.html
PS: Regarding the state-engine, you should always request a state
of "Disconnecting", and let the exiting receiver set it finally
to "StandAlone".
> A side question:
> Should drbd notice when the link comes up? He does not seem to.
>
No, we do not do that. In case we discover that we can not bind()
our address we give up.
-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 :
next prev parent reply other threads:[~2006-10-06 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 21:37 [Drbd-dev] Cstate stays in "Disconnecting" after Heartbeat link down and up Montrose, Ernest
2006-10-06 13:18 ` Philipp Reisner [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-06 13:29 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=200610061518.35416.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