From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-announce@lists.linbit.com
Cc: drbd-user@lists.linbit.com
Subject: drbd-9.1.19-rc.1 and drbd-9.2.8-rc.1
Date: Tue, 27 Feb 2024 22:46:47 +0100 [thread overview]
Message-ID: <86wmqp4m2g.fsf@linbit.com> (raw)
Hello,
As always, this release brings several fixes. For many of those fixes,
we created new test cases or extended existing test cases to verify the
bug's existence and the patch's effectiveness.
What we learned was that we needed more testing in the area of the
checksum-based resync. We have that now.
In December, I wrote that the RDMA transport was ready; well, it turned
out that it still had an issue under heavy I/O load. Although that is
fixed now, other bugs might be waiting to be discovered in the RDMA
transport.
This is the release candidate. Please help test it.
9.2.8-rc.1 (api:genl2/proto:86-122/transport:19)
--------
* Fix the not-terminating-resync phenomenon between two nodes with
backing disk in the presence of a diskless primary node under
heavy I/O
* Fix a rare race condition aborting connections claiming wrong
protocol magic
* Fix various problems of the checksum-based resync, including kernel
crashes
* Fix soft lockup messages in the RDMA transport under heavy I/O
* changes merged from drbd-9.1.19
- Fix a resync decision case where drbd wrongly decided to do a full
resync, where a partial resync was sufficient; that happened in a
specific connect order when all nodes were on the same data
generation (UUID)
- Fix the online resize code to obey cached size information about
temporal unreachable nodes
- Fix a rare corner case in which DRBD on a diskless primary node
failed to re-issue a read request to another node with a backing
disk upon connection loss on the connection where it shipped the
read request initially
- Make timeout during promotion attempts interruptible
- No longer write activity-log updates on the secondary node in a
cluster with precisely two nodes with backing disk; this is a
performance optimization
- Reduce CPU usage of acknowledgment processing
https://pkg.linbit.com//downloads/drbd/9/drbd-9.2.8-rc.1.tar.gz
https://github.com/LINBIT/drbd/commit/c2823c629623594bd6f916b7bc7e55629a790d4d
https://pkg.linbit.com//downloads/drbd/9/drbd-9.1.19-rc.1.tar.gz
https://github.com/LINBIT/drbd/commit/b33129351562fde9407c21a96d5bba01d4cf6ed3
reply other threads:[~2024-02-27 21:46 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=86wmqp4m2g.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