Orphaned private volume after deleting VM

[Johnboy]

1. Clone sys-net to sys-clone-net-1
2. Delete sys-clone-net-1
3. /dev/mapper/qubes_dom0-vm–sys–net–clone–1–private → …/dm-64 # is still available, mountable, has data.
   Looks like it won’t get deleted automatically.
   But there are no other volumes for this VM (root, snap, volatile).
   I am on R4.2.4

Can i manually delete the volume and how?

[unman]

1. Clone sys-net to sys-clone-net-1
2. Delete sys-clone-net-1
3. /dev/mapper/qubes_dom0-vm–sys–net–clone–1–private → …/dm-64 # is still available, mountable, has data.
   Looks like it won’t get deleted automatically.
   But there are no other volumes for this VM (root, snap, volatile).
   I am on R4.2.4

Cannot reproduce on R4.3

Can i manually delete the volume and how?

You could just delete the link and the underlying volume with sudo rm

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

[Johnboy]

Just upgraded to R4.3. Cannot reproduce, too.
Will rm’ing the block special file (253/64) delete the whole volume?

[Johnboy]

I used lvchange -an and lvremove. I hope that’s that.