Search results

Should I file a bug or feature request, eliminating the linked clone option when using a LVM?

I'm confused because the config files are the same with a linked a full clone. I took a CT and did a linked-clone and then full-clone: The linked clone above does not reference a base volume and seems to have the same elements as the full clone below. Is there perhaps different config file...

Using Proxmox 5.2-5 I've read the Proxmox documentation about Full and Linked clones, however two questions remain to be answered. Unless I've missed it in the the PVE GUI, there is no indication that a vm was created as a linked clone, and thus dependent on the parent template. 1. How do you...

I have noticed this problem as well. When I clone a container that has snapshots, the references in the clone to the parental snapshots get copied without cloning the underlying disk volumes new disk lvm-thin volumes. So when I delete one of these snapshots it orphans the snapshot in the other...

I suspected that the logical volume was deleted when the rollback failed snapshot volume wasn't restored. I found source in here: PVE/Storage/LvmThinPlugin.pm So I restored it manually so it wouldn't error out at the rollback step. After this I went back to the PVE UI and rolled it back to s7...

This seems to be on the right path with source code to these processes: http://narkive.com/aEe5siOR

Did you ever figure out how to deal with this?

PVE 4.4-1/eb2d6f1e I tried to rollback a snapshot (id 505) and it failed saying "disk threshold reached, not going to create a new volume" or somesuch... I deleted other unused VMs and deleted snapshots from other VMs to make space. VM 505 was still locked so I used the shell qm unlock utility...

Any follow ups offlist bttd? I have this problem too except on a roll back of a regular vm.