[DRBD-announce] drbd-9.0.25-rc1

Philipp Reisner <[email protected]>
Newsgroups dev.linux.lists.drbd-announce
Message-ID <CADGDV=VGosYqnnL1poLWhb20bchH40akJnddY_aJErojQaCqPg@mail.gmail.com>
Hi,

The main reason to do a release is that with 9.0.25 the overhead submitting
IO got smaller. On some specific hardware the fio results go from IOPS=229k,
BW=896MiB/s to IOPS=370k, BW=1445MiB/s (single DRBD device).
Especially with multiple or many DRBD devices on a single server, the
improvement
might be significant.
Other than that there are a number of bug fixes. None of the fixed bugs was
especially spectacular. Generally speaking update will be recommended
as soon as we have the final release.

This is a release candidate, please help testing it.

Changelog:
9.0.25-0rc1 (api:genl2/proto:86-117/transport:14)
--------
 * fix a race condition between receiving UUIDs and finishing a resync
   that can lead to a false-positive split-brain detection later on
 * fix access after free of peer_req objects, that only happened when
   a resync target node is paused sync source at the same time
 * fix abortion of local state changes in case they can not proceed due
   to loss of connection
 * fix corner cases with reconciliation resync and parallel promote
 * fix an issue establishing a connection when the multipath feature is
   used to connect to a stacked resource without a dedicated service IP
 * fix sometimes a peer-disk state to another resync-target staying Outdated
   after two resyncs from the same sync source node finish
 * fix an (unlikely) deadlock while establishing a connection
 * deactivate the kref_debug code, it has performance implications
 * Introduce the "disconnected" hander; it receives the last connection
   state in the environment variable DRBD_CSTATE

https://www.linbit.com/downloads/drbd/9.0/drbd-9.0.25-0rc1.tar.gz
https://github.com/LINBIT/drbd/commit/bd41626d3fdc7b6f575532020ff9ce1c9c4bf29b

best regards,
 Phil
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.