Distributed Replicated Block Device (DRBD) announcements
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-announce@lists.linbit.com
Subject: drbd-9.2.14-rc.1 and drbd-9.3.0-rc.1
Date: Tue, 27 May 2025 18:47:09 +0200	[thread overview]
Message-ID: <86r00am25u.fsf@linbit.com> (raw)


Hello DRBD users,

I am pleased to announce the release of two new candidates. This time,
we are beginning the 9.3 series. The first new feature is called "resync
without replication". It is beneficial when DRBD resyncs a volume that
is busy handling application I/O requests, especially a write-intensive
workload. With the new behavior, the resync time will be significantly
shorter and result in fewer writes to the resync target.
Among the bug fixes included in these releases, the most critical one
addresses a race condition between very short resyncs (empty resyncs)
and application write requests. The window is small, so it is unlikely
to hit, but the consequence is a write missing on the resync target
node.

This is a release candidate.
The final release will come in a week if everything goes as planned.

9.2.14-rc.1 (api:genl2/proto:86-101,118-122/transport:19)
--------
 * Fix a race condition between write requests and very short resyncs
   that might cause DRBD to fail to resync that racing write.
 * Fix the suspend-IO command so that it waits until all pending
   writes are completed before it returns. From now on, it can be used
   to create consistent snapshots of the primary and the secondary.
 * Improve DRBD's pooling of buffer pages. The old implementation
   stopped freeing any of those buffer pages if the kernel would leak
   a single page reference.
 * Fix corner case CM leaks in the RDMA transport.
 * Fix a warning on recent kernels (RHEL10) regarding DRBD failing to
   set queue parameters for zoned block devices.
 * Dockerfile for RHEL10
 * Compatibility with Linux 6.14 and 6.15

9.3.0-rc.1 (api:genl2/proto:86-101,118-123/transport:19)
--------
 * was forked off between 9.2.12 and 9.2.13
 * Implemented resync without replication and made it the default; the
   previous (drbd-9.2 and earlier) behavior is still available via a
   config option. With that, the resync operation begins with
   mirroring of application writes disabled, and it performs multiple
   resync passes, clearing bits in the bitmap. It enables application
   write mirroring when the resync is nearly complete. That reduces
   the I/O load during resync, and in most cases, it reduces resync
   time.
 * Dropped support for RHEL7 and support for kernels older than 3.10.


https://pkg.linbit.com//downloads/drbd/9/drbd-9.2.14-rc.1.tar.gz
https://github.com/LINBIT/drbd/commit/379607b588d34f474c160d64dc81cb4796144016

https://pkg.linbit.com//downloads/drbd/9/drbd-9.3.0-rc.1.tar.gz
https://github.com/LINBIT/drbd/commit/e0ab757e92e6149a1fbc3bc0c06d86a01090dfee

cheers,
 Philipp

                 reply	other threads:[~2025-05-27 16:47 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=86r00am25u.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