I'm runing Proxmox 4.2 with zfs local storage.
I've created a template we want to use to deploy new machines.
When I clone the template I can choose between Full Clone and Linked Clone. The first one just creates a new zfs block device and copies all the data from the template. The ondisk data of the template block device is not refereced as with a zfs snapshot, although with thin provisioning, the 100GB disk is reduced to around 9GB used space.
If I use linked clone, everything is faster, the clone is created in seconds, the initial used space on the new block device is minimal.
However, even as zfs snapshot are first class citizens and can work independently, proxmox requires the base template disk to be present. Is there any way to "unlink" the clone?
1000 is the first template
1001 is another template based on 1000 (linked cloned and converted to template)
577 and 581 are linked clones
580 is a full clone
I think I can move the disk to another storage and back... but it's very time consuming... There must be some other way around it.
Thanks if you got this far!
Julián.
I've created a template we want to use to deploy new machines.
When I clone the template I can choose between Full Clone and Linked Clone. The first one just creates a new zfs block device and copies all the data from the template. The ondisk data of the template block device is not refereced as with a zfs snapshot, although with thin provisioning, the 100GB disk is reduced to around 9GB used space.
If I use linked clone, everything is faster, the clone is created in seconds, the initial used space on the new block device is minimal.
However, even as zfs snapshot are first class citizens and can work independently, proxmox requires the base template disk to be present. Is there any way to "unlink" the clone?
Code:
# pvesm list zfs
zfs:base-1000-disk-1 raw 107374182400 1000
zfs:base-1000-disk-1/base-1001-disk-1 raw 107374182400 1001
zfs:base-1000-disk-1/vm-577-disk-1 raw 214748364800 577
zfs:base-1000-disk-1/vm-581-disk-1 raw 214748364800 581
zfs:vm-580-disk-1 raw 107374182400 5801000 is the first template
1001 is another template based on 1000 (linked cloned and converted to template)
577 and 581 are linked clones
580 is a full clone
Code:
# zfs list
NAME USED AVAIL REFER MOUNTPOINT
data 133G 2,46T 96K /data
data/zdisks 132G 2,46T 96K /data/zdisks
data/zdisks/base-1000-disk-1 116G 2,56T 12,7G -
data/zdisks/base-1001-disk-1 681M 2,46T 8,99G -
data/zdisks/vm-577-disk-1 3,78G 2,46T 11,8G -
data/zdisks/vm-580-disk-1 8,99G 2,46T 8,99G -
data/zdisks/vm-581-disk-1 3,17G 2,46T 11,0G -
Code:
$ cat /etc/pve/storage.cfg
zfspool: zfs
pool data/zdisks
sparse
content rootdir,imagesI think I can move the disk to another storage and back... but it's very time consuming... There must be some other way around it.
Thanks if you got this far!
Julián.
