From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-announce@lists.linbit.com, drbd-user@lists.linbit.com
Subject: drbd-utils v9.28.0-rc.1
Date: Thu, 25 Apr 2024 09:19:49 +0200 [thread overview]
Message-ID: <ZioEFbCHo4HRU7qq@arm64> (raw)
[-- Attachment #1: Type: text/plain, Size: 2050 bytes --]
Dear DRBD users,
this is the first RC of the upcoming drbd-utils version 9.28.0. In
contrast to the recent releases this one contains a bit more exciting
news:
- 8.3 code is gone
- events2: netlink messages (used between utils in user space and the
kernel module) can be sent out of order. So far this was more
theoretical, but more modern kernels actually seem to actually make
use of it. We put code in place that reorders such messages if sent
out of order. This is particularly important for software that depends
on events2 processing. The actual impact might vary, but just to name
a few that make use of events2 processing: drbd-reactor, drbdmon,
LINSTOR.
- udev: drbdsetup got a new "udev" subcommand that replaces drbdadm's
"sh-udev" command. This allows to have the actual (in kernel) state
reflect the udev state more closely compared to drbdadm which used res
file information. It avoids problems if the res file can not be parsed
or problems if the hostname is not set yet (e.g., systemd-udev starts
before the hostname is set). All in all we hope this solves udev
related issues we saw previously.
there are all kinds of fixes and improvements all over the place like
improved Pacemaker support for 2.1.7, or tweaks for the promotion score
if force-io-error is true, which will help drbd-reactor. More details
can be found in the changelog or the git history.
Please test, if we don't find any bugs the final version will get
released in about a week from now.
Regards, rck
Changelog:
* events2: set may_promote:no promotion_score:0 while
force-io-failure:yes
* drbdsetup,v9: show TLS in connection status
* drbdsetup,v9: add udev command
* 8.3: remove
* crm-fence-peer.9.sh: fixes for pacemaker 2.1.7
* events2: improved out of order message handling
GIT: https://github.com/LINBIT/drbd-utils/commit/5ddb29c18c0a539fb010f883ea4f88bd1d184391
TGZ: https://pkg.linbit.com//downloads/drbd/utils/drbd-utils-9.28.0-rc.1.tar.gz
PPA: https://launchpad.net/~linbit/+archive/ubuntu/linbit-drbd9-stack
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2024-04-25 7:19 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=ZioEFbCHo4HRU7qq@arm64 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox