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.9 AND drbd-utils-9.1.0
Date: Thu, 31 Aug 2017 15:44:54 +0200 [thread overview]
Message-ID: <6130033.TSK9DS0yrj@nuc> (raw)
Hi,
in short, this is a _must_ upgrade for every use that uses DRBD in
the SDS use-case. I.e. with diskless primaries. Two bugs where
identified that can cause DRBD to return wrong data to read
requests on the diskless primary node.
drbd
9.0.9-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 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
* in a cluster with a diskless primary, when a server goes away,
and is not outdated, outdate it upon reconnect. This gets done
when it's current UUID does not match the diskless primaries
exposed data UUID; with this bug present it can lead to
inconsistent data presented on the diskless primary node to
readers
* fix update of exposed data UUID on diskless primaries. It could
lead to false reject of further diskfull secondaries that
want to join
* 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 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
* Speed up down of many resources by using call_rcu() instead
of synchronize_rcu()
* Make it compatible with the soon to be released 4.13 kernel
http://www.linbit.com/downloads/drbd/9.0/drbd-9.0.9-1.tar.gz
https://git.linbit.com/drbd-9.0.git/tag/refs/tags/drbd-9.0.9
drbd-utils
9.1.0
--------
* allow events2 --now polling
* fix ambiguous inheritance for peer-device-options
* fixup fallback path for BLKZEROOUT for older kernels
* fix v9 proxy support
* modernized XEN scripts
* reproducible builds support
* create-md --force for v8.4 (for compat to v9)
* fix cstate output
* resize: give resize more time (same as attach)
* drbdmon: peer-device status, version info, node name
* "drbdadm status" for v8.4
* set peer-device-options only once
http://www.linbit.com/downloads/drbd/utils/drbd-utils-9.1.0.tar.gz
https://git.linbit.com/drbd-utils.git/tag/refs/tags/v9.1.0
reply other threads:[~2017-08-31 13:44 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=6130033.TSK9DS0yrj@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.