Andrei Kvapil

Hi, today I faced with the same issue again: ```bash # linstor r l -r one-vm-7510-disk-0 ╭────────────────────────────────────────────────────────────────╮ ┊ ResourceName ┊ Node ┊ Port ┊ Usage ┊ Conns ┊ State ┊...

I also tried to create another replica: ```bash # linstor r c m10c34 one-vm-7510-disk-0 -s thindata SUCCESS: Successfully set property key(s): StorPoolName SUCCESS: Description: New resource 'one-vm-7510-disk-0' on node 'm10c34'...

btw after removing both replicas and restarting linstor-controller the new replicated created fine: ```bash # linstor r c m10c33 one-vm-7510-disk-0 -s thindata SUCCESS: Successfully set property key(s): StorPoolName SUCCESS: Description:...

Hey @ghernadi, we're not put `v1.8.0` to production cluster yet.

On the nodes still a lot of `Inconsistent` resources in `Connecting` and `Unconnected` states: ``` root@hf-kubevirt-02:/# drbdadm status pvc-4520ca42-4d53-4879-b662-63fd1f3ae4e3 pvc-4520ca42-4d53-4879-b662-63fd1f3ae4e3 role:Secondary hf-kubevirt-01 connection:Connecting ``` ``` root@hf-kubevirt-01:/# drbdadm status pvc-4520ca42-4d53-4879-b662-63fd1f3ae4e3 pvc-4520ca42-4d53-4879-b662-63fd1f3ae4e3...

After restarting it is still stuck, but now another error, lvm timed out: The most interesting, that `data/tgt108_00000` already not existing in my system [ErrorReport-5BB322C9-CDA0B-000000.log](https://github.com/LINBIT/linstor-server/files/2436958/ErrorReport-5BB322C9-CDA0B-000000.log) [ErrorReport-5BB322C9-CDA0B-000001.log](https://github.com/LINBIT/linstor-server/files/2436959/ErrorReport-5BB322C9-CDA0B-000001.log)

@ghernadi, sure, there is logs from another node, with the same problem: [ErrorReport-5BAF8C77-12FF9-000000.log](https://github.com/LINBIT/linstor-server/files/2436972/ErrorReport-5BAF8C77-12FF9-000000.log) [ErrorReport-5BAF8C77-12FF9-000001.log](https://github.com/LINBIT/linstor-server/files/2436973/ErrorReport-5BAF8C77-12FF9-000001.log)

> This 5-second-timeout-disconnect bug is fixed. In the current release? I've tried to repeeat `lvremove -f data/tgt108_00000` manually, it was executing little more than 5 second. > Nice catch, thank...

Hi, we just faced with the same situation (on 1.7.1): ```bash # linstor r l -r pvc-9ed4b88e-3ba3-400c-bf9b-4750a3384b6b pvc-f8aa2cba-8784-4a21-b8c1-fc192272d8d9 pvc-7fbdf685-39b0-43b9-80f3-a2bbe0e144a4 -a +-------------------------------------------------------------------------------------------------+ | ResourceName | Node | Port | Usage |...

my bad `No space left on device` was meaning rootfs but not a storagepool itself, it was overfilled on m1c6, but anyway I guessing you'd like to handle this error...