> My guess what's happening here is this:
> Either the local node or some remote node that it can still successfully
> connect to while initializing the local DRBD was either not stopped, or
> the DRBD kernel module on it did not stop the resource successfully.
> Therefore, some node still had siz
It seems that some of the size values have changed compared to the
original problem report:
On 7/25/19 5:59 PM, Paul Clements wrote:
> ~]# size_gb=71680
> [root@sios0 ~]# lvcreate -n $LV -L ${size_gb} $VG
> Logical volume "my_lv" created.
> [root@sios0 ~]# lvs
> LVVGAttr LSize
Hi GIanni,
we get around 20Gbit/s over iperf with Kernel 5 with the untuned iperf
command.
Sorry, that i didn't mention that.
Network seems to be completly fine. We don't have any packet drops or
similar too.
Thanks,
Alex
Am 26.07.19 um 11:50 schrieb Gianni Milo:
> Hi Alexander,
>
> Do you get
Hi Alexander,
Do you get same behaviour when using other tools like iperf for example ?
if so, then this might be not related to the DRBD itself, but due to
ethernet drivers issues for example..
Gianni
On Thu, 25 Jul 2019 at 13:26, Alexander Karamanlidis <
alexander.karamanli...@lindenbaum.eu
Hi,
just to give some more information an lshw from the Servers:
https://pastebin.com/3E7N898R
Thanks in advance,
Alex
Am 25.07.19 um 14:18 schrieb Alexander Karamanlidis:
> Hi everyone,
>
>
> so we upgraded to PVE6 (Proxmox VE 6) about a week ago to test it.
>
> Since then our DRBD resource go
