[DRBD-user] drbd-9.0.15-0rc2

[Roland Kammerer]

Hi,

Here is rc2 of the soon to be released 9.0.15. Changes between rc1 and
rc2 include:

9.0.15-0rc2 (api:genl2/proto:86-114/transport:14)
--------
* fix tracking of changes (on a secondary) against the lost disk of a
  primary and also fix re-attaching in case the disk is replaced (has
  new meta-data)

* New module parameter to disable support for older protocol
  versions, an in case you configured peers that are not expected to
  connect it might have positive effects because then this node does not
  need to assume that such peer is ancient

* compat for v4.18 kernel

http://www.linbit.com/downloads/drbd/9.0/drbd-9.0.15-0rc2.tar.gz
https://github.com/LINBIT/drbd-9.0/commit/d21aee7bdf8ecd074ab60ff406bbc5a5e57bc13e

Thanks for the reports so far, please keep testing.

Thanks, rck

Changes from rc1:

On Fri, Jul 20, 2018 at 04:17:36PM +0200, Philipp Reisner wrote:
> Hi,
> 
> Another DRBD release is coming up. Please help in testing the release
> candidate.
> 
> This release contains one important fix for users that use DRBD9
> in combination with LINSTOR or DRBDmanage and intend to do live
> migrations of VMs.
> 
> What is in for everyone is the performance optimization, giving the
> users of NVMe SSDs up to 30% more IOPs.
> 
> 9.0.15-0rc1 (api:genl2/proto:86-114/transport:14)
> --------
>  * fix live migrate of VMs on DRBD when migrated to/from diskless
>    nodes; before that fix a race condition can lead to one of the nodes
>    seeing the other one as consistent only
>  * fix an IO deadlock in DRBD when the activity log on a secondary runs full;
>    In real world this was very seldom triggered but can be easily reproduced
>    with a workload that touches one block every 4M and writes them all in
>    a burst
>  * fix hanging demote after IO error followed by attaching the disk again
>    and the corresponding resync
>  * fix DRBD dopping connection after an IO error on the secondary node
>  * improve details when online changing devices from diskless to with disk and
>    vice versa. (Including peers freeing bitmap slots)
>  * remove no longer relevant compat tests
>  * expose openers via debugfs; that helps to answer the question why does
>    DRBD not demote to secondary, why does it give tell me "Device is held
>    open by someone"
>  * optimize IO submit code path; this can improve IOPs up to 30% on a system
>    with fast backend storage; lowers CPU load caused by DRBD on every workload
> 
> http://www.linbit.com/downloads/drbd/9.0/drbd-9.0.15-0rc1.tar.gz
> https://github.com/LINBIT/drbd-9.0/commit/fc844fc366933c60f7303694ca1dea734dcb39bb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20180806/e167db61/attachment.pgp>