Hi all,
all back!
I just realized the line does not offer 19Mbit/s but instead only
4Mbit/s and then the value is to be expected.
Sorry for confusion!
/Christian
Am 31.07.2019 um 06:48 schrieb kn...@knebb.de:
> Hi all,
>
>
> I have a drbd device set up and it looks like it is running fine
Hi all,
I have a drbd device set up and it looks like it is running fine so far.
Just when watching /proc/drbd the resync seems to be really, really slow:
version: 8.4.11-1 (api:1/proto:86-101)
GIT-hash: 66145a308421e9c124ec391a7848ac20203bb03c build by mockbuild@,
2018-11-03 01:26:55
1: cs:Sy
On 29/07/2019 10:34, Eddie Chapman wrote:
Hello,
I've managed to corrupt one of the drbd9 resources on one of my
production servers, now I'm trying to figure out exactly what happened
so I can try and recover the data. I wonder if anyone might understand
what went wrong here ( apart from the
This did not work.
On Jul 24, 2019, at 9:03 AM, Banks, David (db2d)
mailto:d...@virginia.edu>> wrote:
Tried adding new drbd.service file below. In the middle of a data transfer now
but will try a reboot when done.
[Unit]
Description=DRBD -- please disable. Unless you are NOT using a cluster m
On Sat, Jul 27, 2019 at 02:43:31PM -0400, Digimer wrote:
> Hi all,
>
> I hit an odd issue. I have a 3-node DRBD 9 setup (see below).
> Basically, two nodes are protocol C and in pacemaker, the third node is
> protocol A and is outside pacemaker (it's a DR and will periodically
> connect -> sync