ghernadi

Just to make sure - all of these resources are `-l drbd,storage` (which is the default if you have nothing specified), no nvme or something else involved, right?

The issue you show in the first comment / description - was that before or after the controller restart? If it was after, I assume it was also after "the...

Quick update, `v1.8.0-rc1` contains a fix for a bug that might be the root cause of this duplicated node-id bug. I would appreciate if you could test it, although I...

Did this error occur since `v1.8.0-rc1`?

I will look into this, but can you please re-upload ErrorReport-5BAFAC32-CDA0B-000000.log, as it has the same content as ErrorReport-5BAFAC32-CDA0B-000001.log

Alright, the `NullPointerException` is already fixed, included in the next release. The "Access to deleted resource" is most likely a consequence of the previous `NullPointerException`. However, the `NullPointerException` triggered this...

> In the current release? No, sorry, it is fixed internally and will be in the next release...

Hehe, I guess linstor was also not able to generate the ErrorReport due to `No space left on device`? :) But yes, I will think about what we could do...

Hi! The trace logs from https://github.com/LINBIT/linstor-server/issues/19#issuecomment-765385008 does not really help as that shows only that the controller set the DELETE flags on rsc and vlm, but not why the satellite...

> the resources got stuck at Negotiating. Can you show us some `dmesg` from `local-worker2`, especially regarding DRBD and those two resources? `Negotiating` comes from DRBD. Linstor is only displaying...