Le 02/10/2018 à 19:56, Radoslaw Garbacz a écrit :
> Hi,
>
>
> I have a problem, which (from what I found) has been discussed, however not in
> the particular case, which I experienced, so I would be grateful for any
> suggestions of how to deal with it.
Your problem sounds pretty similar to a re
Hi,
I've inherited a setup that has been running for a very long time,
but this morning both were down, and showed:
[root@node-01 ~]# drbd-overview
0:drbd0 StandAlone Secondary/Unknown Inconsistent/Outdated r-
1:drbd1 Connected Secondary/Secondary UpToDate/UpToDate C
r-
[roo
Hi,
I have a problem, which (from what I found) has been discussed, however not
in the particular case, which I experienced, so I would be grateful for any
suggestions of how to deal with it.
I.
1. I get an error when demoting DRBD resource:
* drbdadm down data0
data0: State change failed: (-1
Not sure if it's related, but I had a similar issue on one of my PVE hosts
recently. I have the same kernel installed on all (3) nodes, but this
machine was locking up after a few minutes with the softlockup messages you
were getting. The only way to recover was to hard reboot the machine.
Managed
Le 02/10/2018 à 11:31, Rene Peinthor a écrit :
> Hi Everyone!
>
> This mostly a bugfix release, one change that needs mentioning is that
> all delete commands will now wait until the resource is actually deleted on
> the
> satellites.
Great, thank you !
> linstor-server 0.6.5
>
Le 02/10/2018 à 11:31, Rene Peinthor a écrit :
> Hi Everyone!
>
> This mostly a bugfix release, one change that needs mentioning is that
> all delete commands will now wait until the resource is actually deleted on
> the
> satellites.
Great, thank you !
> linstor-server 0.6.5
>
Hi Everyone!
This mostly a bugfix release, one change that needs mentioning is that
all delete commands will now wait until the resource is actually deleted on
the satellites.
linstor-server 0.6.5
* Fix: Thin drivers often didn't correctly skip the initial sync
* Fix: ZFST
