From: Johannes Khoshnazar-Thoma <johannes.thoma@linbit.com>
To: drbd-announce@lists.linux.dev
Subject: WinDRBD 1.2.13 / LINBIT SDS 1.0.4 released
Date: Fri, 11 Sep 2026 15:48:44 +0200 [thread overview]
Message-ID: <2ece8073-e380-43bb-96ac-b5922f28392b@linbit.com> (raw)
Dear WinDRBD community,
We released WinDBD 1.2.13 and LINBIT SDS 1.0.4 today. WinDRBD comes with
some minor fixes, which are (also) a result of our in-depth regression testing
with WinDRBD these days. We continue to make as many tests for Linux DRBD run
with WinDRBD also. Since behaviour of the Windows kernel differs from the Linux
kernel a new class of defects in DRBD is also encountered. WinDRBD 1.2.13 comes
with DRBD 9.2.19 and 9.3.3 as DRBD engines. There is no urgent need to upgrade
WinDRBD, unless you are affected by one of the changes:
* DRBD 9.2.19 / DRBD 9.3.3
* Honor GFP_ZERO flag, thereby fixing unneccessary resyncs
* Export DRBD's fault injection framework
* Honor send timeout on connect
For the LINBIT SDS release 1.0.4, this is based on LINSTOR 1.35.0+,
LINSTOR GUI 2.6.0, and WinDRBD 1.2.13. Furthermore there have been
many improvements on the OCF resource agents (like ipaddr2 does not
need the nic= parameter, filesystem does not need the hyper-v parameter),
so if you are planning on deploying a highly available hyper-v cloud,
it is recommended to use this latest 1.0.4 SDS release for it.
Furthermore, our documentation specialist Michael Troutman is preparing
a comprehensive guide "Highly Available Hyper-V with LINBIT SDS for Windows
Getting Started Guide" (which has already 80 pages!), I am really looking
forward to this release of the guide. When it is out I will write a
separate announcement mail.
Best wishes,
- Johannes
reply other threads:[~2026-09-11 13:48 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=2ece8073-e380-43bb-96ac-b5922f28392b@linbit.com \
--to=johannes.thoma@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.