Andrei Kvapil

I have same problem but with different reason: ``` # linstor s l | grep DELETING | one-vm-140-disk-2 | snapshot-0 | m1c4, m1c6 | 0: 3 GiB | DELETING |...

Can I remove this snapshot forcefully somehow? - It is not existing anymore in backing lvm datastore.

Yes, it can't be removed because linstor tries to merge it: ``` # linstor r l -r one-image-46 +-----------------------------------------------+ | ResourceName | Node | Port | Usage | State |...

No, resource is not deleted yet, but snapshot is ``` # linstor rd l -R one-image-46 +-----------------------------+ | ResourceName | Port | State | |-----------------------------| | one-image-46 | 7108 |...

Sure **Satellite 1:** [m1c4.log](https://github.com/LINBIT/linstor-server/files/3295985/m1c4.log) [ErrorReport-5D07516B-16A3B-000000.log](https://github.com/LINBIT/linstor-server/files/3295988/ErrorReport-5D07516B-16A3B-000000.log) [ErrorReport-5D07516B-16A3B-000001.log](https://github.com/LINBIT/linstor-server/files/3295989/ErrorReport-5D07516B-16A3B-000001.log) [ErrorReport-5D07516B-16A3B-000002.log](https://github.com/LINBIT/linstor-server/files/3295991/ErrorReport-5D07516B-16A3B-000002.log) **Satellite 2:** [m1c6.log](https://github.com/LINBIT/linstor-server/files/3295993/m1c6.log) [ErrorReport-5D075214-85D84-000000.log](https://github.com/LINBIT/linstor-server/files/3295994/ErrorReport-5D075214-85D84-000000.log) [ErrorReport-5D075214-85D84-000001.log](https://github.com/LINBIT/linstor-server/files/3295995/ErrorReport-5D075214-85D84-000001.log) [ErrorReport-5D075214-85D84-000002.log](https://github.com/LINBIT/linstor-server/files/3295996/ErrorReport-5D075214-85D84-000002.log)

> the only way I could reproduce this issue was manually removing the snapshot, which I hope you did not do It might be, I was try to delete this...

> Edit: In case one-image-46 only has test-data which can be thrown away, you can also remove that resource instead of modifying the database. You might have to restart the...

```bash # linstor r d m10c33 one-vm-7430-disk-0 SUCCESS: Description: Node: m10c33, Resource: one-vm-7430-disk-0 marked for deletion. Details: Node: m10c33, Resource: one-vm-7430-disk-0 UUID is: 1d22b4c5-fe07-4a93-9432-3b8220d05cd2 SUCCESS: Notified 'm15c30' that 'one-vm-7430-disk-0' is...

> I guess this is not reproducible and you also do not remember if you had some controller-restarts involved in this issue? At this time I was trying to put...

yes exactly, thus: - controller was working fine - I've added 1500 diskless resource to storage10 - then controller was restarted - then it's started loading resources on storage10 during...