Dear WinDRBD users,
We just released a new version of WinDRBD: 1.1.19. The only difference
to 1.1.18 is that an optimization that was implemented in 1.1.8 (speeding
up initial bitmap read on attach) was patched out since it caused troubles
on certain setups with storage backend throtteling. If yo
Dear WinDRBD community,
I just release another WinDRBD release. This release contains a
fix in the cygwin DLL library that should fix the hanging drbdadm
processes that can happen when they are executed from a
Windows service and a normal session in paralell. Unless you
are affected by this bug t
Dear WinDRBD community,
We just released WinDRBD 1.1.17. It contains a refactored implementation of
how WinDRBD handles disk timeouts. In this version WinDRBD has its own timer
and if that timer elapses it compiletes all I/O requests pending with an error
status. To DRBD it looks just like the di
Dear WinDRBD users,
We just released WinDRBD 1.1.16 which fixes a reason for a BSOD
(system crash) when there are 4 billion I/O requests submitted to
WinDRBD. While this seems to be a large number it has already
been triggered by an installation in the field. The fix corrects both
the counter of
Dear WinDRBD users,
I am announcing a new WinDRBD stable release: 1.1.15. It fixes
a very rare corner case where Windows starts swapping out
kernel mode thread's stacks, which might cause a list corruption
on the events list. The patch to WinDRBD 1.1.15 simply disables
stack paging for WinDRBD th
Dear WinDRBD users,
Today we released WinDRBD 1.1.14 which contains a small bugfix
of the drbdmeta utility. For external meta data drbdadm create-md
now clears the whole block device thereby ensuring that there
are no leftover bits set in the bitmaps.
The WinDRBD driver itself has not changed ex
Dear WinDRBD users,
Today we released WinDRBD 1.1.12, a release mainly target at users that
use fencing instead of quorum in order to avoid split brain. There are
3 patches to DRBD included (one of which even made it into the
upstream drbd-9.1 and drbd-9.2 branches of DRBD) as well as
several sma
Dear WinDRBD users,
In this release of WinDRBD where we put lots of efforts to make
WinDRBD behave more stable under memory pressure. The older
WinDRBD releases gave up without retrying when (for example)
kmalloc() could not allocate memory. The new version contains
a retry loop in the memory all
Dear WinDRBD users,
I just released WinDRBD 1.1.9. It contains many fixes for corner cases. Usually
you should not be affected by those, so there is no urgent need to upgrade
if you have a running WinDRBD instance. For details about the fixes (and also
fixes for the 1.1.8 release), please read th
Hi,
You can write a simple cmd script (drbdadm up / drbdadm primary)
and have it executed via task manager at system startup time.
(try cmd /c myscript.cmd)
Alternatively you can use LINSTOR For Windows which also
will start the resource on satellite startup (which is started
also on system star
Dear WinDRBD users,
WinDRBD release 1.1.7 is out, the main new features are:
.) A blue screen that might trigger when memory allocation fail at
a specific code path was fixed.
.) A performance bug introduced in WinDRBD 1.0.0-rc11 was fixed.
Reason was that the TCP/IP nodelay option was no
Dear WinDRBD Users,
I just released a new minor version of WinDRBD. In particular,
ReFS as a file system upon a WinDRBD device was fixed (broken
since 1.1.0). There is no urgent need to upgrade WinDRBD unless
you need some of the features/fixes below.
From the WHATSNEW.md file:
What's new in ve
Dear WinDRBD users,
This is a hotfix release for a bug that was introduced in 1.1.4. If one has
disks larger than about 2TB accessing them might not work. If you are
using WinDRBD 1.1.4 please upgrade now.
The signed installer can be downloaded from the LINBIT website:
https://linbit.com/linbit
Dear WinDRBD users,
This is another point release for WinDRBD. It fixes a rare BSOD which
happens when the WinDRBD installer fails to upgrade WinDRBD. Usually
this succeeds so there is no urgent need to upgrade now. In addition
the logger service is stopped later so we also get the driver unload
Dear WinDRBD users,
This is a point release that fixes a blue screen of death (BSOD) that
may happen when resources that were Primary are brought down and
immediately brought up again. It is recommended for users who are
already on the 1.1.X branch to upgrade to this 1.1.2 version. You can
do so
Dear WinDRBD users,
We just released WinDRBD 1.1.1 - it is the same source as 1.1.0 but the
version number has changed. It is released as a convenience for those
who installed WinDRBD 1.1.0 before Oct 28 (which had a signature bug).
Upgrading from those 1.1.0 versions to 1.1.1 should work without
Dear WinDRBD users,
We became aware of an issue in the installer install-windrbd-1.1.0.exe,
published on Oct 25. It won't install unless you have testsigning enabled
(which you should not enable).
We updated the installer on the WebSite (it should show October 28 as date)
as a hotfix and will pu
cluster can be upgraded without service
interruption. Also note that a reboot should not be neccessary.
We would love to hear your feedback via the mailing list or directly
at the LINBIT site.
Best regards,
- Johannes Thoma
___
Star us on GITHUB: https
Dear DRBD and WinDRBD users,
This is another release canidate which fixes two minor issues: from the
WHATSNEW.md:
Fixed drbdadm adjust: Don't always detach / attach
Fixed drbdsetup hang: there is a timeout in stable_state_change now
Again, please help testing this release canidate, you can do
Dear DRBD and WinDRBD users,
This is another release canidate for the WinDRBD 1.1 branch. It
fixes a rare BSOD where there is still I/O in flight when drbdadm
secondary / drbdadm down is run. This bug was discovered by
a user from India and shows how important your feedback about
WinDRBD usage is
Dear DRBD and WinDRBD users,
This is another release canidate for the 1.1 branch of WinDRBD.
It mainly contains bugfixes and the installer already knows
about LINSTOR: it will stop and start again the linstor-satellite
on upgrade (if it exists).
Also we fixed an issue with using existing data. S
aking build possible on Linux only (using Wine for
the Windows part).
Best wishes and please let us know about feature requests, bug reports and more
stuff regarding WinDRBD, either on github or by eMail,
- Johannes Thoma
___
Star us on GITHUB:
Dear WinDRBD users,
Yesterday I copiied the wrong file which resulted in an errnous version of
the WinDRBD installer (1.1.0-rc1) to be on the linbit download site. The
error was that upgrading from 1.0.X to 1.1.0-rc1 didn't work correctly.
It was "just" an installer issue but today we replaced th
Dear WinDRBD users,
This is the first release canidate for the new windrbd 1.1 branch. The major
change in 1.1 is that the driver is signed directly by Microsoft which should
make it run with SecureBoot enabled. To get a driver signed by Microsoft,
certain tests (hardware lab kit - HLK) must be p
Dear DRBD and WinDRBD users,
This is a minor release of WinDRBD in which logging to the kernel logfile when
drbdadm status is run is removed. We had a user that ran drbdadm status every
5 seconds which ended up in a 70 GB logfile with mostly useless information.
Unless you are running drbdadm sta
Dear WinDRBD users,
We are releasing a minor update to WinDRBD 1.0.0 which contains two changes:
The timeout for user mode helper scripts has been dropped from the kernel
module.
This allows scripts to run longer than the previously hardcoded 10 seconds. They
now may take as long as they like.
Dear DRBD and WinDRBD users,
Finally we are releasing WinDRBD 1.0.0, the first stable production-ready
version of WinDRBD after almost 5 years of development. This is an
important milestone in WinDRBD development. Technically it is
the same as the last rc20 release canidate with a few extra DRBD
Dear WinDRBD users,
This is a new release of WinDRBD which contains 2 minor fixes as
well as an upgrade to the newest upstream DRBD version 9.0.32.
From the WHATSNEW.md file:
---
Fixed a bug that triggered invalid page chain assertion and lead to
connection abort at the beginning of sy
Dear WinDRBD users,
There is a new release canidate in which two reasons for bluescreens (BSODs) are
fixed. One happened in earlier releases when a resync is running for a longer
time
(such as syncing 16TB volumes) the other one was a blue screen that happened
sometimes on network interruptions
Dear WinDRBD users,
1.0.0-rc17 contains a bug introduced in 1.0.0-rc14 which is now
fixed there is this 1.0.0-rc18 release. It was a bluescreen which
happens sometimes when syncing larger amounts of data.
Also upgrading without reboot now should run more smooth and
the user mode services (windrbd
Dear DRBD and WinDRBD users,
We are proud to release WinDRBD 1.0.0-rc17 with many new features: most
notably no reboots on upgrading are required any more (when upgrading
from 1.0.0-rc17 to an upcoming newer version).
As far as I am concerned this rc is feature complete for the stable 1.0.0
vers
Dear WinDRBD and DRBD community,
We just released WinDRBD release canidate 1.0.0-rc16 which is
mainly a bug fix release. It fixes an issue on the SCSI disk
interface which caused backing devices between 1 and 2 TB
in size not to work properly. If you plan to use WinDRBD with
backing devices of ab
Dear WinDRBD and DRBD community,
We are happy to announce another -rc: 1.0.0-rc15. In this release a
thread leak is fixed that caused a thread being started and never terminated
on each connection attempt. If you face system unstableness when a
resource is in Connecting state you should upgrade t
Dear WinDRBD and DRBD users,
This is a small update of WinDRBD. It now supports writing to the Windows
Event Log (see the windrbd utility's help text). Also more parts of CygWin
come along with the EXE installer (sed, simple bash, ..) so that running
truck based replication should be possible now
Dear WinDRBD and DRBD users,
We are happy to announce another -rc of WinDRBD. The past 2-3
months I have spent a lot of time fixing bugs uncovered by driver
verifier. Driver verifier is enabled when running tests via
the Windows Hardware Lab Kit (HLK) which in turn is required to
obtain a certifi
Dear DRBD and WinDRBD users,
We just released another rc: 1.0.0-rc12. This is a special release because in
this
release 3 bugs that affected system stability were fixed. This rc12 ran within
a disconnect / connect loop via Windows firewall and I/O for 5 days without
issues (releases up to rc11 u
Dear DRBD and WinDRBD users,
We've just released another version of WinDRBD: This one is 1.0.0-rc11.
It is now based upon DRBD 9.0.28 which is the most recent (stable) version
of DRBD. It also contains a fix of a bug that caused blue screens or system
lockups when disconnecting. Also we now slow
Dear DRBD and WinDRBD users,
We've just released another release canidate of WinDRBD: 1.0.0-rc10. This
version contains an
optimization on the network receiver side which speeds up secondary writes by a
factor of 2-4. It also contains fixes for various BSODs.
For now there are two registry keys
Dear DRBD and WinDRBD users,
We've just released a new release canidate version of WinDRBD: as always
the installer of WinDRBD 1.0.0-rc9 can be downloaded from:
https://www.linbit.com/linbit-software-download-page-for-linstor-and-drbd-linux-driver/#windrbd
Below is the abstract from the WHATSNE
Dear WinDRBD and DRBD users,
We've just released WinDRBD 1.0.0-rc8 with a few bug fixes in the Emulation layer.
Especially these fixed system hangs at various places (such as hang in
invalidate-remote loop), please see the closed issues on github for details. Also
device sizes > 2 TB are now w
Dear WinDRBD and DRBD users,
We've just released WinDRBD 1.0.0-rc7, which is now based on DRBD 9.0.25 and
therefore contains the latest patches from the upstream DRBD source. We are
getting closer to 1.0.0, so please help testing these releases these days,
As always the WinDRBD install package
Dear WinDRBD and DRBD users,
In release 1.0.0-rc6 several issues in the workqueue implementation were fixed
which causes most (but not all) reasons for BSOD's when disconnecting while
syncing to be fixed. Also the ko count mechanism, a feature that makes
connections more stable was fixed.
As
Dear DRBD and WinDRBD users,
WinDRBD 1.0.0-rc5 has been released.
You can download the installer (signed with SHA256 from now on) from:
https://www.linbit.com/linbit-software-download-page-for-linstor-and-drbd-linux-driver/#windrbd
A lot has happened since the last 1.0.0-rc1 release, mainly pa
Dear DRBD and WinDRBD users,
This is the first release canidate of the upcoming 1.0.0 release of the WinDRBD
driver and userland utilities. Please download a signed driver (signed by
Linbit) from the Linbit software download page:
https://www.linbit.com/linbit-software-download-page-for-linsto
Dear DRBD and WinDRBD community,
We proudly present WinDRBD 0.10.7: it has a set of new features that improve
usability and feature completeness (compared to the Linux version of DRBD).
Among the new features are:
Online verify (with crc32c checksum algorithm): Check if both backing devices
c
Dear DRBD and WinDRBD users,
Exactly 10 years ago, Linbit announced a version of their DRBD
replication software for Microsoft Windows (see
https://fghaas.wordpress.com/2010/04/01/its-coming-drbd-for-windows/)
What was an April fool's joke then is today released in version
0.10.6 which is becomi
Dear DRBD and WinDRBD users,
We've just released WinDRBD 0.10.5. The main difference is
that the DRBD URI used to configure the WinDRBD boot device
is now key/value based making it easier to read and more
importantly easy to extend. It will learn new keywords as
WinDRBD evolves but the principle
Hi,
Just wanted to check if you could solve the performance
issues, and if yes how you solved them.
Kind Regards,
- Johannes
Am 29.01.20 um 15:05 schrieb Johannes Thoma:
Hi Max,
Thank you for testing WinDRBD.
Am 29.01.20 um 06:02 schrieb Max Bergmann:
Hi drbd-users,
Recently, I've
Dear DRBD and WinDRBD community,
We just released a new minor release of the WinDRBD software
package. For those who don't know, WinDRBD is a port of
DRBD to the Microsoft Windows family of operating systems.
We mainly focussed on getting WinDRBD more stable for
this release, we have two (non-bo
Hi Max,
Thank you for testing WinDRBD.
Am 29.01.20 um 06:02 schrieb Max Bergmann:
Hi drbd-users,
Recently, I've been testing windrbd, but I can't seem to achieve more than 100
Mbps (~12mb/s) throughout, even thought the network between my nodes is 1Gpbs
or more, with a simple UNC share betwe
Dear DRBD and WinDRBD community,
There is a quick fix release for WinDRBD: 0.10.3.
It fixes logging. Starting from 0.10.0 the syslog_ip
was hardcoded to an IP address which probably does
not exist on your setup. With WinDRBD 0.10.3 logging
to localhost should work again as expected.
To start the
Dear DRBD and WinDRBD community,
There is a new release of WinDRBD: 0.10.2. It is mainly
targeted to those experimenting with the boot feature as
it contains a new ipxe binary which passes the DHCP address
to the Windows system. Windows will configure the boot NIC
at boot time based on the info i
Hi Gianni,
Thank you for your eMail, please see the comments inline.
Am 06/11/19 um 21:24 schrieb Gianni Milo:
Thanks for this. Booting from a diskless Windows installation is a very
interesting feature.
I'm curious to know if there are future plans having a combination of
diskful/diskless W
Dear DRBD and WinDRBD community,
We are happy to announce a new version of WinDRBD: 0.10.1
This version mainly fixes the use of non-boot devices which
are not implemented in 0.10.0. If you are using data devices
(devices created with 0.9.2 or before) you can now upgrade
to this version.
In 0.10
Dear DRBD and WinDRBD community,
It's been about 6 months since the last WinDRBD version
(0.9.2) was released. The reason for such a long development
cycle is that we finally managed to implement system root
("C:\") atop a WinDRBD device.
In order to do so, we had to reengineer the device layer
d over the WinDRBD driver we expect MS SQL server
to run then. However we are probably not finished with the
implementation before Q1. I will keep you updated.
Best Regards,
- Johannes Thoma
___
Star us on GITHUB: https://github.com/LINBIT
drbd-user ma
Hi Trevor, Hi John,
Am 19.08.19 um 14:27 schrieb Trevor Hemsley:
On 19/08/2019 13:07, john smith wrote:
> Hi Johannes
>
> Thank you for your reply.
>
> Is write error related to logical block size of the disk?
>
No, it is just that an IoCtl isn't implemented. Some of them
are undocumente
gards
From John Smith
With kind regards,
- Johannes Thoma
___
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user
Hi Junnam,
Am 26.04.19 um 13:30 schrieb 박준남:
Hi Johannes,
I'm using DRBD for backup
You can do that, however DRBD is meant more for high availability
use cases than for backup.
The reason we need VSS is to use the snapshot function to recover data that is
a problem later.
With WinDRBD y
Hi 박준남,
Thank you for testing WinDRBD. What exactly are you
trying to build?
Am 22.04.19 um 09:12 schrieb 박준남:
Hi
I tested windrbd 0.9.2.
I found some features that are not available:
1. windrbd can not support vss(volume shadow copy) on primary
2. windrbd can not support unc path on prima
works, what does not work yet
and what we plan to implement next.
KNOWN-BUGS: During our endurance tests we discovered some
issues which are documented in this file.
In order to get professional support for WinDRBD please contact
sa...@linbit.com
Thank you for improving WinDRBD by using it.
- Joh
works, what does not work yet
and what we plan to implement next.
KNOWN-BUGS: During our endurance tests we discovered some
issues which are documented in this file.
In order to get professional support for WinDRBD please contact
sa...@linbit.com
Thank you for improving WinDRBD by using it.
- Joh
Hi Kamal,
Thank you for your bug report concerning WinDRBD. Sorry for
the late answer I was on vacation last week.
i have two windows 2016 standard server.
when data coming in flow on primary, i failed my secondary server.
result my primary server crash and reboot.
How exactly did you fail th
ke the doc say I have
>
> config.status: error : cannot find input file: user/config.h.in
>
> I'v search and googled it ... no clue .
>
> Thanks for help.
>
> Olivier
>
Hi,
Seems that autoheader is missing .. run autoheader and then retry,
hope that helps,
- Johannes
drbd-user
Maybe you want to have a look at drbd-proxy (see
http://www.linbit.com/en/products-services/drbd-proxy)
Please contact sa...@linbit.com for an evaluation license.
Best regards,
- Johannes
--
: DI. Johannes Thoma
: LINBIT | Your Way to High Availability
: Tel. +43-1-8178292-0, Fax +43-1-8178
drbd-user
Maybe you want to have a look at drbd-proxy (see
http://www.linbit.com/en/products-services/drbd-proxy)
Please contact sa...@linbit.com for an evaluation license.
Best regards,
- Johannes
--
: DI. Johannes Thoma
: LINBIT | Your Way to High Availability
: Tel. +43-1-8178292-0, Fax +43-1-8178
66 matches
Mail list logo
