* drbd-9.2.21 and drbd-9.3.5
@ 2026-11-18 7:59 Philipp Reisner
0 siblings, 0 replies; only message in thread
From: Philipp Reisner @ 2026-11-18 7:59 UTC (permalink / raw)
To: drbd-announce
Hi,
The DRBD-9.3.5 release brings two new features. First, it adds an
interface to use one of DRBD’s change-tracking bitmaps to support backup
software. Together with the new drbd-utils release, it adds new commands
to enable, reset, and dump tracked changes in an extent-list
format. This is compatible with what many backup software programs can
consume to optimize taking incremental backups. To get this to backup
software, LINSTOR will also support it, and our integrations with
Kubernetes, OpenStack, OpenNebula, and Apache CloudStack (and others if
possible) will support passing the CBT information as well.
The second new feature worth mentioning is a reworked RDMA transport. It
is called rdma2, and it builds on recent work (released with drbd-9.3.1)
allocating receive buffers in large chunks. Under optimal conditions,
that means with large BIOs, I saw lab machines maxing out a 100Gbps link
using Connext-X5 cards while replicating a write stream with DRBD.
Another change is completely transparent for you as users. We are
switching the netlink family to drbd2. This is an important step for
bringing drbd-9 to upstream Linux. It will allow us to have a drbd-9 in
upstream Linux that is compatible with very old drbd-8.4 drbd-utils.
On top of that, the release includes a large number of bug fixes. We
fixed many bugs identified by the community and by us at LINBIT, as we
use more and more LLMs to analyze events in DRBD clusters.
9.3.5 (api:genl2/proto:86-101,118-125/transport:23)
--------
* Track changed blocks for incremental backups: a tracking bitmap slot
records every write to the backing device; cbt-flush and cbt-start
bracket a snapshot taken while I/O is suspended on all nodes
* suspend-io now also waits for the barrier ack of the last epoch, so
that with protocols A and B the writes are on the peers' stable
storage too; flush-to-peers=no skips that wait
* Add rdma2, a new RDMA transport that moves all data with one-sided
RDMA-WRITE, sends bios zero-copy, and fails over to a surviving path
when a link goes down
* Serve the new drbd2 netlink family next to the drbd family
* Optionally serve DRBD 8.4 userland over the netlink family at version
1 (CONFIG_DRBD_NL_DRBD1, rpmbuild --with nl_drbd1,
DEB_BUILD_OPTIONS=nl_drbd1); off by default
* Fix lb-tcp skipping a path for good after the peer closed it first
during a disconnect, which starved every later handshake
* Fix spurious and racy "bitmap locked" warnings when bitmap operations
on different peer slots run concurrently
* Serve changed block tracking on the drbd netlink family too, so that
it works on kernels without the drbd2 family (before 6.2)
* Fix a Primary staying Ahead after the congestion clears: the peer
stayed Outdated and no resync started until the next write
* Fix rdma breaking every resync with data on kernels before 5.1
(RHEL 8.2)
* All fixes from 9.2.21
- Fix writes that completed with success but never reached a peer, or
that a later resync overwrote: a frozen write toward a peer that got
the new data generation from a third node, a write admitted just
before a peer was lost, and frozen writes resumed by a state change
that also starts an io-error policy
- Fix the receiver waiting forever for application writes after the
link is lost: during a handshake bitmap change, a bitmap slot clear
or copy, a weak-source switch, a peer demotion, an online resize
commit, and on P_SIZES
- Fix a resync target returning at the predecessor of a deferred new
current UUID, which left a diskless Primary suspended
- Fix a Primary and an UpToDate Secondary at equal current UUIDs never
connecting, and two such nodes that become stable together waiting
in WFBitMapT
- Fix a block missing after a power loss with external meta data: flush
the backing device before an AL transaction evicts an extent
- Fix a slow start of every resync on kernels before Linux 6.3 with
bio-based backing devices (LVM), and the resync queue of a slow
backing device growing without bound with c-min-rate 0
- Fix a sync source running out of memory when the sync target
requests faster than it can read: a target with rs-discard-granularity
keeps its requests within max-buffers, and the source allocates the
pages of a resync read only when it submits the read
- Fix resyncs in opposite directions stopping for good with
max-parallel-resyncs: only the requesting side takes a slot
- Fix an attaching node waiting in WFBitMapT forever while its peer
decided there is nothing to sync
- Fix a failed local write-zeroes leaving the old data on a disk that
stays UpToDate
- Fix auto-promote giving up long before auto-promote-timeout
- Fix disconnect: the peer going to NetworkFailure instead of
Disconnecting, and "drbdadm disconnect" failing with -18 when the
peer tears down first
- Fix TLS: two nodes stalling in the handshake until the TLS timeout,
and going StandAlone when the peer resets the connection during the
handshake
- Fix a use-after-free of the rdma control timer on teardown
- Fix the build on kernels before 4.17 (RHEL 7) and with Linux 7.4,
and the send buffer not growing during a resync on Linux 7.4
- Fix a resync target staying Inconsistent with nothing left to sync:
when the Primary cannot reach the sync source, after aborting a weak
sync source, and when P_RS_CANCEL_AHEAD overtakes the Ahead state
change
- Fix a reconciliation resync target waiting in WFBitMapT forever, and
out-of-sync bits from before a lost diskless Primary being dropped at
equal dagtags
- Fix a peer's connect-time upgrade from Outdated going unnoticed,
which left writes unreplicated
- Fix an Outdated sync source being marked UpToDate after a resync
with failed blocks
- Fix the day0 slots, a regression in 9.2.20: forget-peer left a slot
that the next UUID bump filled with a later generation, and a peer
created from the day0 UUID could be refused as unrelated data;
attach repairs such meta data
- Fix promoting a peer that holds an older generation of the data a
diskless Primary exposes
- Fix P_OUT_OF_SYNC: never sent for Primaries with node-id 8 or higher,
a crash after del-peer of a Primary, and writes left pending for a
peer that lost its connection
- Fix the activity log: AL updates turned off while a crashed Primary
resyncs, the superblock written too late on "al-updates no", and the
in-core AL not written when AL updates come back on
- Fix a dry-run connect (--tentative) establishing the connection
without a resync
- Fix the last close returning before the peers have the last write on
stable storage, and auto-demote failing on a pending signal
- Fix call-pri-lost-after-sb killing the receiver instead of demoting
- Fix online resize: drain application I/O before the commit and before
a participant replies, cache the peers' size answers per volume, and
refuse a too small peer while syncing from a larger one
- Fix a receiver deadlock at the end of a resync when the link fails
while the bitmap is written, and bound the memory a bitmap write-out
holds
- Fix resync pacing: the fixed resync-rate (c-plan-ahead 0) holds, the
resync queue at the backing device is bounded so application I/O does
not wait behind it, and DRBD logs when max-buffers or c-max-rate
limit a resync
- Fix connect and disconnect issues: a spurious NetworkFailure right
after a handshake, a stale ping timeout dropping the next connect, a
peer's close while connecting taken as a network error, ko-count 0
being counted down, and a second peer accepted beside a DRBD 8.4 peer
- Fix lb-tcp: a NULL pointer dereference in the receiver, a CPU spin
when the peer closes mid-payload, zero-length data chunks, hot-adding
paths, and listeners left on unused paths
- Fix rdma: use-after-free and refcount underflows on teardown during
connect, a 60 s hang after a failed establish, going StandAlone on an
interrupted connect, and a crash with a peer running rdma2
- Fix the TLS handshake compat code (upstream fixes): leaks, refcount
and use-after-free bugs, and a missing admin check on DONE
- Fix memory corruption by peer_device flags on 32-bit kernels
- Fix a negative ap-in-flight after a resend, BarrierAck count warnings,
sending on after a send failed, and an unsent packet flushed at
disconnect ("Wrong magic value" on the peer)
- Fix attach hanging after the node was a verify target, and a double
release when linking the holder fails
- Show the submit and sent ages of requests in debugfs again, and mark
peer writes that completed locally
- Fix building SUSE KMPs on SLES 16, and the build with
CONFIG_DRBD_TIMING_STATS
https://pkg.linbit.com//downloads/drbd/9/drbd-9.3.5.tar.gz
https://github.com/LINBIT/drbd/commit/b85d6fd444480f63070f8003b288151af0a9eb11
https://pkg.linbit.com//downloads/drbd/9/drbd-9.2.21.tar.gz
https://github.com/LINBIT/drbd/commit/91232a5e4a391bd3975c8cd0a0a70ad959997d67
cheers,
Phil
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-11-18 8:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-18 7:59 drbd-9.2.21 and drbd-9.3.5 Philipp Reisner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox