Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Lars Ellenberg <Lars.Ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] it is (mostly) working again (for me)
Date: Wed, 13 Sep 2006 16:10:11 +0200	[thread overview]
Message-ID: <20060913141011.GD1387@barkeeper1.linbit> (raw)

ok, fixed a few stupid things now.

at least it is "working" again, meaning
 it survived a few disconnect/reconnect cycles
 while resyncing _and_ writing data at the same time,
 without triggering any asserts or suspicous kernel messages.

I hit a "hang" once (probably a race related to the "inc_net" stuff)
when reconnecting (got stuck in the bitmap exchange).
recoverd with no problem when I disconnected the secondary again.
reconnected again, no problem this time.

so, I guess we are back on track again,
to go for the real bugs :)

(like all those unconditional dereferencing of mdev->bc)

cheers,

-- 
: Lars Ellenberg                                  Tel +43-1-8178292-55 :
: LINBIT Information Technologies GmbH            Fax +43-1-8178292-82 :
: Schoenbrunner Str. 244, A-1120 Vienna/Europe   http://www.linbit.com :

                 reply	other threads:[~2006-09-13 14:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20060913141011.GD1387@barkeeper1.linbit \
    --to=lars.ellenberg@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