May 29, 2020 - I use LVM-thin as the main storage and have repeatedly noticed that cloning VMs or recovering using proxmox often means that the VM is broken if LVM-thin is used as the target storage.

LVM thin is a block storage, but fully supports snapshots and clones efficiently.

April 14, 2022 - ... i always get problem with adding disk and the solution quite easy is to just boot over a partition manager soft and create lvm there. Then reboot and hop all detect in prox. ... i always get problem with adding disk and the solution quite ...

I setup a single 120GB SSD non-UEFI computer with the storage defaults (Not ZFS). I customized a great many things and then used a HDD duplicator to clone to a 250GB destination disk. To my surprise the cloned... ... Hi ! Proxmox is great and i'm pretty new with this mix of technologies. LVM is extremely powerful and i need to deal with it to increase , wisely , a thin pool without breaking anything.

September 23, 2021 - You must not use lvm-thin in shared storage configuration - its not safe and will cause data corruption. You can use LVM (thick), but there will be no snapshot support. Either you have to create a LUN per virtual disk and pass it through directly ...

June 9, 2026 - Workaround that works every time: skip qm clone, dd the volumes directly. qm create 103 --name test --ostype win11 --machine pc-q35-11.0 \ --bios ovmf --memory 4096 --cores 4 --sockets 1 --cpu host \ --scsihw virtio-scsi-single --net0 ...

September 22, 2022 - Click to expand... when try full ... "vm-116-disk-0" created. ... LVM-thin is the exception - linked clones in LVM thin are fully independent of their base image (each can be deleted without interfering with the oth...

November 29, 2017 - LVM thin is a block storage, but fully supports snapshots and clones efficiently.

April 19, 2022 - It may not display this or other websites correctly. You should upgrade or use an alternative browser. ... After adding a new 1tb SSD to a proxmox server, have been having an unusual issue, hoping someone might have suggestions on where to go next. Symptom is that if I try to clone or copy to this new lvm-thin ...

Previous message (by thread): [pve-devel] Sparse clone/move over a thin LVM ? Next message (by thread): [pve-devel] [PATCH] qemu-img convert : use default cache=unsafe instead writeback · Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] >>* From lvm thin to qcow2: >>Since lvm-thin doesn't catch SEEK_DATA/SEEK_HOLE it'll consider the >>entire device as being allocated and reaches the slow path for detectin >>zeroes, this part should still work however and the qcow2 file should be >>smaller.

March 20, 2025 - qm create 907 --name debian12-cloudinit --description "Debian 12 cloud-init template" --template 1 --ostype l26 --machine q35 --cpu host --scsihw virtio-scsi-single --scsi0 local:0,iothread=1,discard =on,backup=off,format=qcow2,import-from=/root/debian-12-generic-amd64.qcow2 --tablet 0 --boot order=scsi0 --scsi1 local:cloudinit --ciupgrade 0 --net0 virtio,bridge=vmbr10 When I clone (full) template (with disk on local storage in qcow2 format) and start the vm, the startup stuck : Problem seems to be related to LVM-Thin and raw format but I'm not sure about that. Has anyone reproduce same errors

April 29, 2025 - Click to expand... Right, it is an "unusedX" disk in the VM 185 config. If I recall correctly, in the local thin-LVM environment the LVs are not actively deactivated by PVE. But in thick-LVM - they are. I don't know how Op did the transfer.

June 10, 2020 - Dear friends, I am having some trouble while cloning VM to LVM-Thin, but able to place disk image in LVM-Thin. Please share your experience with me in regards to a similar encounter. Proxmox Version: 6.2-4 Error: UPID:dr01:00000B65:0000ECEE:5EE0A528:qmclone:1000:root@pam: 1 5EE0A6E4 clone failed: command '/sbin/lvs --separator : --noheadings --units b --unbuffered --nosuffix --options lv_size /dev/pve/vm-400-disk-0' failed: got timeout LVM-Thin Capacity 1.7TB Hardware: DELL PowerEdge R710 (16 Cores, 64GB RAM) Drive Type: RAID5 500GB x 6 Units + 1spare

August 21, 2025 - Disclaimer: Yes, I should have looked this up beforehand, it is listed in various places: Clonezilla does not properly back up LVM thins. I might have missed it, but I didn't see it in the proxmox documentation itself. I had to replace the disks for that hold the boot sector of my proxmox...

March 25, 2020 - Click to expand... and it's only possible create a full clone. Is there anything I'm missing here? ... Regular LVM does not support thin clones - only full ones.

January 31, 2018 - Linked Clones works for theses storages: files in raw, qcow2, vmdk format (either on local storage or nfs); LVM-thin, ZFS, rbd, sheepdog, nexenta.

July 26, 2018 - On lvm-thin all clones are independent, that's why it is possible to delete the parent.

December 24, 2021 - Hi! I just cloned PM SSD disk 128G to SSD 256G. LVM partition was resized while cloning. Device Start End Sectors Size Type /dev/sda1 2048 4095 2048 1M BIOS boot /dev/sda2 4096 528383 524288 256M EFI System /dev/sda3 528384 500117503 499589120 238.2G...

January 4, 2017 - Then fresh thin one is created and _started_: # lvs | grep 102 vm-102-disk-1 pve Vwi-a-tz-- 15.00g data 12.29 It get's moved to another LVM thin VG and becomes fat right away. # lvs | grep 102 vm-102-disk-1 pvesata Vwi-aotz-- 15.00g datasata 100.00 So basically thin LVM is not really thin when one uses disk migration in order to move VM's in order to do maintenance on host which is what every good admin should do.

Hello I have a new small proxmox pve System on an old ACER / Gateway Server with an entry level ACER / Gigabyte Mainboard. There is only one Container which does not start. A LVMthin Install, no ZFS. The last thing I have done was to clone the Proxmox System SSD to a second and same SSD, 1:1...