From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-announce@lists.linbit.com
Subject: [DRBD-announce] drbd-0.7.21.tar.gz
Date: Wed, 2 Aug 2006 11:49:14 +0200 [thread overview]
Message-ID: <200608021149.14996.philipp.reisner@linbit.com> (raw)
Hi There,
After we where pointed at the "syncer stalled" after reconnect symptom.
Lars tested disconnect/reconnect in a tight loop. This brought up
some issues, we fixed.
0.7.21 (api:79/proto:74)
-----
* Fixed the "syncer stalled" after reconnect symptom.
* Fixed the "stalled in WFParams" after reconnect symptom. The cause
of this bug was actually a misuse of the data socket.
* Allow to set the uplug_watermark to 1, only usefull for very strange
cases.
This makes DRBD to cause no troubles, in case the replication link
is badly broken...
http://oss.linbit.com/drbd/0.7/drbd-0.7.21.tar.gz
http://svn.drbd.org/drbd/tags/drbd-0.7.21/
http://www.linbit.com/support/drbd-0.7.21/ (completed in about 2 hours)
-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-08-02 9:49 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=200608021149.14996.philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=drbd-announce@lists.linbit.com \
--cc=drbd-user@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.