From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-announce@lists.linbit.com, drbd-user@lists.linbit.com
Subject: [DRBD-announce] drbd-utils-9.11.0
Date: Wed, 16 Oct 2019 13:48:07 +0200 [thread overview]
Message-ID: <20191016114807.GD2194@rck.sh> (raw)
[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]
Hi DRBD users,
This release contains some bug fixes and some new features. The features
were mainly driven by customer requests, so they solve some specific
corner cases. If you don't use these features (or a pretty recent
kernel), there is no urgent need to upgrade now.
Highlights include:
- There were changes in netlink for Linux 5.2. If you use one of these
kernels, you should update. This change is shared between utils code
for versions 9.0 and 8.4 of the kernel code.
- rr-conflict got a retry-connect option. This is particularly useful in
setups where quorum and pacemaker are used. See the according commit
msg.
- drbdsetup got an option to force resync which, on new-current-uuid'
set the current data set UpToDate and forces a resync to all peers.
- drbdmon got a 256/16 color mode.
Overall the changes are pretty small, so I'm almost sure it won't kill
you kittens. The new versions can be found on the usual locations.
9.11.0
--------
* drbdsetup,all: prepare for netlink changes (linux v5.2+)
* drbdadm,v9: fix a check for setting up connections multiple times
* init: setup file backed loop devices (mapping from LINSTOR)
* rr-conflict: add retry-connect option (>=drbd 9.0.20)
* drbdmon: 256/16 colors; events2 handler improvements
* drbdsetup,v9: new flag: force-resync (>=drbd 9.0.21)
https://www.linbit.com/downloads/drbd/utils/drbd-utils-9.11.0.tar.gz
https://github.com/LINBIT/drbd-utils/tree/v9.11.0
https://launchpad.net/~linbit/+archive/ubuntu/linbit-drbd9-stack
Regards, rck
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2019-10-16 11:48 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=20191016114807.GD2194@rck.sh \
--to=roland.kammerer@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.