On Thu, Jan 30, 2020 at 08:04:30AM +0530, Mona Sinha wrote:
> Hi,
>
> We are using DRBD version: 8.3.8.1. Sometimes during the load test, we see
> that full sync is occurring and could not find the reason behind it. Could
> someone please help us?
DRBD 8.3 is EoL for many, many, many, many,
Hi,
We are using DRBD version: 8.3.8.1. Sometimes during the load test, we see
that full sync is occurring and could not find the reason behind it. Could
someone please help us?
Following are the logs:
DS1 server logs:
Aug 16 09:43:48 ds1 kernel: block drbd0: sock was shut down by peer
Aug 16
Well (ironically?) you have me wondering if my approach may have issues
I simply have not encountered, possibly due to good luck, so I am
interested in hearing from others whether I should reconsider my approach...
I received a lot of invaluable help from the list, and in particualr one
very
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
Robert Altnoeder
> For a cluster with nodes A, B, C, where A is the node where the snapshot
> is restored to the backend device, a possible process is:
> - on B, drbdadm disconnect resource
> - on B, drbdadm invalidate resource
> - on C, drbdadm disconenct resource
> - on C, drbdadm invalidate
Paul O'Rorke
> I don't know what others do, I just do essentially what you said, but
> without stopping the DRBD service. I simply restore the snapshot to the
> primary DRBD block device, not the backing device and let DRBD do it's
> magic in the background.
>
>
thanks a lot for your hint.
