Distributed Replicated Block Device (DRBD) announcements
 help / color / mirror / Atom feed
From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-announce@lists.linux.dev
Subject: drbd-utils v9.36.0
Date: Wed, 18 Nov 2026 13:14:39 +0100	[thread overview]
Message-ID: <av2Wr_LwbPwgT-bS@arm64> (raw)

[-- Attachment #1: Type: text/plain, Size: 3307 bytes --]

Dear DRBD users,

this is the final version of drbd-utils 9.36.0. There have been no
changes since rc.2

Regards, rck

GIT: https://github.com/LINBIT/drbd-utils/commit/e25b7d4d17e53811c6fd57f3ae7add0b9028cced
TGZ: https://pkg.linbit.com//downloads/drbd/utils/drbd-utils-9.36.0.tar.gz
PPA: https://launchpad.net/~linbit/+archive/ubuntu/linbit-drbd9-stack

Changelog:
9.36.0
-----------
 * drbdadm: raise the default cmd-timeout-short from 5 to 10 seconds;
   keep the medium and long defaults that were in effect (600, none)
 * drbdadm: show changed cmd-timeout-* settings in the v9 dump
 * drbdadm: fix adjust failing silently when a wait-connect lasted
   longer than the remaining cmd-timeout of the preceding connect
 * drbdmeta: keep the bitmap provenance feature of DRBD 9.2.20 and 9.3.4
   when writing the superblock; apply-al after a crash cleared it, and
   DRBD then counted a crashed Secondary's activity log bits as set for
   blocks its peers lack
 * drbdmeta: forget-peer makes the freed bitmap slot a day0 slot, a
   copy of one or all bits set, as the kernel does
 * drbdmeta: cbt-dump --mode=dirty|zero also reports the extents never
   written since create-md, from the day0 bitmap; "format": 1; the
   extents are start and length and cover the volume, as in ovirt-imageio
 * drbdmeta: cbt-dump on a dm-thin volume takes the zero extents from
   the mappings of the thin pool, which, unlike the day0 bitmap, know
   about discards; with external meta data, --data-device (drbdadm:
   --data-snapshot) names the snapshot of the backing device
 * drbdmeta: fix apply-al skipping the last activity log extent of the
   device as beyond the end of the bitmap, so that extent was not
   resynced after a crash of the Primary; since 9.33.0
 * drbdmeta: apply-al reports the amount it marked out of sync
   correctly; it reported 0 KB with up to 128 KB per bitmap bit, and
   counted bits past the end of the device
 * drbdsetup: use the "drbd2" netlink family when the kernel offers
   it, fall back to "drbd"; DRBD_NETLINK_FAMILY forces one
 * drbdsetup,drbdadm: drive a DRBD 9 module that advertises 8.4 over
   drbd2; use the 8.4 tools only for a genuine DRBD 8.4 module
 * drbdsetup: hand drbd-8.4 command lines to drbdsetup-84 instead of
   translating them to DRBD 9 requests
 * drbdsetup,drbdadm: add the changed block tracking commands
   cbt-flush, cbt-start, cbt-stop, cbt-status and cbt-dump; suspend-io
   waits for the last barrier ack, --flush-to-peers=no skips the wait
 * drbdmeta: keep the changed block tracking bookmark across
   superblock rewrites, add cbt-dump
 * drbdmeta: converting v08 meta data of a crashed primary to v09 keeps
   it a crashed primary, so DRBD 9 resyncs its activity log extents
 * drbdadm,adjust: fix a recreated proxied peer stuck in Connecting;
   rebuild its proxy connection when a peer or path is new
 * drbdadm: fix require-drbd-module-version-{lt,le,gt,ge}; for example,
   requiring 9.2.0 or later accepted a 9.1.0 or 8.4.11 module
 * libgenl: report the kernel's extended ACK text on netlink errors
 * drbdsetup: add attach --discard-my-data to resolve a split brain
   detected when attaching to a connected device
 * spec: enable SELinux on SLES 16+; require bash-completion only
   conditionally; no rich pacemaker dependency on SLES 12

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2026-11-18 12:14 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=av2Wr_LwbPwgT-bS@arm64 \
    --to=roland.kammerer@linbit.com \
    --cc=drbd-announce@lists.linux.dev \
    /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