From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-announce@lists.linbit.com
Cc: drbd-user@lists.linbit.com
Subject: [DRBD-announce] drbd-9.0.9rc1
Date: Fri, 04 Aug 2017 23:26:30 +0200 [thread overview]
Message-ID: <5852518.3AtK2rx97R@nuc> (raw)
Hi,
good news for the weekend, the next drbd-9 release will be ready
in one week.
Get your test equipment ready next week, and let us know if you
find anything suspicious.
This release will be very important for users that have diskless,
primary nodes in their setups.
drbd
9.0.9rc1-1 (api:genl2/proto:86-112/transport:14)
--------
* fix occasionally forgotten resyncs in installations where
diskless primaries are present. The bug tigers when a storage
node is re-integrated, and it happens to connect to the diskless
primary first; This bug is severe, since it might cause inconsistent
data read back on the diskless primary!
* fix a possible OOPS when in a debug message regarding bitmap
locking
* fix discard bigger than 1MiB; The bug causes disconnect with
bigger discard requests
* fix an issue that causes unexpected split-brain situations upon
connect. This issue triggers only when one of the node has a
node_id bigger than 3.
* fix left over bits in bitmap on SyncSource after resync; the
issue was triggered by write requests that come in while the
resync starts
* fix peers becoming unexpectedly displayed as D_OUTDATED at the
end of a resync; While the disk state on the node stays D_UP_TO_DATE
* fix a race between auto promote and auto demote of multiple volumes
in a single resource; The symptom was that the a process opening
the /dev/drbdX for read-write gets an -EROFS errno
http://git.drbd.org/drbd-9.0.git/tag/refs/tags/drbd-9.0.9rc1
http://www.linbit.com/downloads/drbd/9.0/drbd-9.0.9rc1-1.tar.gz
best regards,
Phil
reply other threads:[~2017-08-04 21:33 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=5852518.3AtK2rx97R@nuc \
--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.