Determining whether a disk is possibly the base for a linked clone

Lovepump

New Member
Mar 3, 2020
1
0
1
57
I've recently removed an old unused template VM (VE version 5.3-5), yet a disk that was associated with the VM ID still resides on the local storage (lvm).

I would like to free up the storage associated with this old template, yet I'm uncertain if the old template was used to create any linked clones.

I have a newer template VM that has disks associated with it, however when I shell to the Proxmox-VE server and list them (with lsblk) the template disks have names like:

pve-base--<vmid>--disk--0

The disk still associated with the former template doesn't have the word "base" in it, and is listed like the other VM disks, ala:

pve-vm--<vmid>--disk--0

Is it safe to remove this "leftover" disk if Proxmox-VE didn't remove it when I removed the template VM?
Will Proxmox-VE complain if the disk happens to be the base for a linked clone when I try to remove it?

Additionally, I attempted to discover how linked clone disks are listed (both in the Proxmox-VE UI as well as via shell with lsblk) by creating a new linked clone from my newer template VM. However, there doesn't seem to be any indicator (via the web-based UI) that the clone is a linked clone from either. The block file sizes for the linked clone are the same as those of the template disk

Is there a good way to tell?

Thanks!
 
I've recently removed an old unused template VM (VE version 5.3-5), yet a disk that was associated with the VM ID still resides on the local storage (lvm).

I would like to free up the storage associated with this old template, yet I'm uncertain if the old template was used to create any linked clones.

I have a newer template VM that has disks associated with it, however when I shell to the Proxmox-VE server and list them (with lsblk) the template disks have names like:

pve-base--<vmid>--disk--0

The disk still associated with the former template doesn't have the word "base" in it, and is listed like the other VM disks, ala:

pve-vm--<vmid>--disk--0

Is it safe to remove this "leftover" disk if Proxmox-VE didn't remove it when I removed the template VM?
Will Proxmox-VE complain if the disk happens to be the base for a linked clone when I try to remove it?

As long as you configure everything by WEB GUI (or Proxmox CLI) Proxmox VE will complain and refuse removing.

But if made some manual interventions (in config files etc.) it is not suer any more. However, a disk-base which is used for clones can usually not be delted at all since the Storage (LVM, Ceph) refuses.

Additionally, I attempted to discover how linked clone disks are listed (both in the Proxmox-VE UI as well as via shell with lsblk) by creating a new linked clone from my newer template VM. However, there doesn't seem to be any indicator (via the web-based UI) that the clone is a linked clone from either. The block file sizes for the linked clone are the same as those of the template disk

Is there a good way to tell?


AFIACS you use LVM-thin storage, in this case

Code:
lvs

will show you possibly existing dependencies.
[/QUOTE]