From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-announce@lists.linbit.com
Cc: drbd-user@lists.linbit.com
Subject: drbd-9.1.23-rc.1 and drbd-9.2.12-rc.1
Date: Mon, 11 Nov 2024 15:44:18 +0100 [thread overview]
Message-ID: <861pzhj0e5.fsf@linbit.com> (raw)
Hello DRBD-users,
This DRBD release is about four weeks late compared to the usual
release pace. The reasons for this are that the discovery of fresh
bugs was a bit slow in this cycle, and those bugs were hard to
crack. It took some time to understand both bugs to the extent that it
allowed us to write reproducers for our test suite.
By the way, the customer affected by one of these issues run more
than 22,000 drbd resources in a linstor cluster stretching over more
than 350 nodes, with about 7.9 PB under LINSTOR management.
The DRBD RDMA transport depended on the behavior of the Melanox
cards. We fixed that and verified the improvements by running it on
intel RDMA cards.
Last but not least, we invested quite some time in tracking all Linux
upstream developments and have DRBD compatible with 6.11 and the
not-yet-released 6.12 kernels.
I intend to branch off a new series (e.g., 9.4.x) soon, and I will no
longer do releases in the 9.1.x branch.
We will discontinue support for RHEL7 kernels (and distros equally
old) with the new branch. We will add performance improvements for the
data path, features for multi-site deployments, and an optionally new
way of doing resyncs.
Please help test the release candidates.
https://pkg.linbit.com//downloads/drbd/9/drbd-9.2.12-rc.1.tar.gz
https://github.com/LINBIT/drbd/commit/1eeb1fcfccbabfaf2d22a376c1f1a2a90eda3b2b
https://pkg.linbit.com//downloads/drbd/9/drbd-9.1.23-rc.1.tar.gz
https://github.com/LINBIT/drbd/commit/19a7625af848b7c310b1707060b00ca0773db109
reply other threads:[~2024-11-11 14: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=861pzhj0e5.fsf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox