The volume is in the DELETING state

[marafon607]

Version of LINSTOR
The controller: linstor controller 1.31.2; GIT-hash: 6a9a4bb
The client: linstor-client 1.25.4; GIT-hash: 93ec1f097c91645a6f0357b264e0f771ffaeeb34

Clear description of the error:
Отчеты об ошибках, логи и выводы команд приложены.

Описать шаги воспроизведения не возможно. В какой-то момент у нас возник алерт что ресурс потерял кворум. В выводе команды "linstor r l" часть том была в состоянии Unknown или Deleting. После ряда попыток восстановления было принято решение удалить ресурс. Сейчас все находятся в состоянии Deleting.

On all nodes:
drbdadm status pvc-8e0e3cf9-e74e-4a8a-8b08-5b878e43d9a9
'pvc-8e0e3cf9-e74e-4a8a-8b08-5b878e43d9a9' not defined in your config (for this host).

6A5F572B-54B1D-008621.txt
6A5F5723-88E5F-008245.txt
6A608FEA-6FD80-005521.txt
Logs-2026-07-27 09_53_52.txt
other.txt

pvc-8e0e3cf9-e74e-4a8a-8b08-5b878e43d9a9.res_tmp.txt

[ghernadi]

All 3 ErrorReports show a LINSTOR internal bug. You will not be able to get out of this bug without restarting the corresponding satellite(s).

Also you are running LINSTOR 1.31.2, which is about a year old. Chances are that the root cause was already fixed in the meantime. Please try to upgrade LINSTOR and see if this issue still persists.

[marafon607]

Unfortunately, restarting the satellite did not help. Can such errors indicate network problems between nodes? Is there any way to check this?
With the update to linstor controller 1.33.3, the problem is also relevant.

[ghernadi]

Can such errors indicate network problems between nodes?

No.

Unfortunately, restarting the satellite did not help.

What do you mean with "did not help"? Can you please elaborate a bit here?
In general the easiest way to fix the error Layer 'STORAGE did not delete the volume <nr> of resource <rsc_name> properly is to restart the satellite. Since you received such an error message at least on nodes ml-1, ml-2 and tag-4118, those satellite should at least be restarted. Once that is done, please try to remove the resource again:

linstor r d intel-1 intel-2 ml-1 ml-2 tag-4118 tag-915 pvc-8e0e3cf9-e74e-4a8a-8b08-5b878e43d9a9

If the resource was removed on some of these nodes but still remain in DELETING on other nodes, please retry the command on the remaining nodes. Once all resources are deleted you should also be able to fully delete the entire resource-definition using linstor rd d pvc-8e0e3cf9-e74e-4a8a-8b08-5b878e43d9a9.