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.3.2-rc.1 and drbd-9.2.18-rc.2
Date: Tue, 14 Apr 2026 22:19:36 +0200	[thread overview]
Message-ID: <86jyu9nvl3.fsf@linbit.com> (raw)

Hi,

Another release coming. This time, it includes important fixes for
large, dynamic LINSTOR clusters. Linstor 1.33.2 already contains fixes
for most cases, but for disaggregated setups with diskless primary
nodes, this DRBD update is also necessary.

The bugs affect resources that got a replica added later, after creation
time. It only affects thinly-provisioned volumes, and only if they never
had a write request with a node absent and fully utilized peer
slots.
So, usually only a small percentage of all resources are
affected. Unfortunately, the affected resources show UpToDate/UpToDate,
but the younger replica misses some blocks.

Now we have tests for all those scenarios.

As these fixes are important for such larger LINSTOR installations, I
start this release cycle about two weeks earlier than usual.

And yes, due to a build issue we noticed late, it is rc.2 of 9.2.18,
while 9.3.2 is rc.1.

At the moment, this is a release candidate.

9.3.2-rc.1 (api:genl2/proto:86-101,118-124/transport:21)
--------
 * Use genl pre_doit/post_doit for netlink request setup and teardown
 * Handle recv returning 0 (EOF) in recv_bio
 * Revert flush_send_buffer send error causing state change
 * All fixes from 9.2.18
  - Fix UUID bump for intentional-diskless primary
  - Fix a_lost_peer_is_on_same_cur_uuid after primary restart
  - Fix new-current-uuid --clear to reset all bm_uuid, not just
    currently configured
  - Detect and recover from split-brain at attach
  - Skip new-region resync for zero-guarantee backends at attach
  - Read bitmap before drbd_determine_dev_size during attach
  - Require rs_discard_granularity for day0 no-resync path
  - Fix missing disk line in drbdsetup show while in D_NEGOTIATING state
  - Use two-phase commit for disconnect even without volumes
  - Count detached-but-connected peers as diskless for quorum
  - Fix out-of-bounds access
  - Fix variable dereference before check

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

https://pkg.linbit.com//downloads/drbd/9/drbd-9.2.18-rc.2.tar.gz
https://github.com/LINBIT/drbd/commit/46e5aef8f574a0fe4ea6d89b2406e507788f07d4

cheers,
 Philipp

                 reply	other threads:[~2026-04-14 20: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=86jyu9nvl3.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