Linked Clones Failing to Create

[jskube]

Every time I try and create a linked clone from a template I get the following error -

create linked clone of drive virtio0 (VM_Images:base-100-disk-2)
stmfadm: data file error
TASK ERROR: clone failed: command '/usr/bin/ssh -o 'BatchMode=yes' -i /etc/pve/priv/zfs/10.220.60.2_id_rsa root@10.220.60.2 /usr/sbin/stmfadm create-lu -p 'wcd=true' -p 'guid=600144ff11dedf124180739fac742f26' /dev/zvol/rdsk/SAN/base-100-disk-2/vm-101-disk-2' failed: exit code 1
​

I originally tried this with ZFS over iSCSI with Nexenta and then changed over my SAN backend to Omnios and I get the same error. I am running Proxmox 4.2-18/158720b9 and can provide any other requested information.

 

[redtex]

+ 1
The same

proxmox-ve: 4.2-64 (running kernel: 4.4.16-1-pve)
pve-manager: 4.2-18 (running version: 4.2-18/158720b9)
pve-kernel-4.4.13-1-pve: 4.4.13-56
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.8-1-pve: 4.4.8-52
pve-kernel-4.4.13-2-pve: 4.4.13-58
pve-kernel-4.4.15-1-pve: 4.4.15-60
pve-kernel-4.2.8-1-pve: 4.2.8-41
pve-kernel-4.4.16-1-pve: 4.4.16-64
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-44
qemu-server: 4.0-86
pve-firmware: 1.1-9
libpve-common-perl: 4.0-72
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-57
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.6.1-2
pve-container: 1.0-73
pve-firewall: 2.0-29
pve-ha-manager: 1.0-33
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.4-1
lxcfs: 2.0.3-pve1
cgmanager: 0.39-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
zfsutils: 0.6.5.7-pve10~bpo80

 

[redtex]

Hello ?
Bump.....

 

[mir]

I have tried some debugging with this issue and the conclusion is that it is a regression probably caused by the abstraction done with the zfs_pool plugin. I will create a bug report in bugzilla.

Main problem:
Original VM:
lrwxrwxrwx 1 root root 0 Sep 25 18:26 /dev/zvol/rdsk/vMotion/base-124-disk-1 -> ../../../..//devices/pseudo/zfs@0:56,raw
After conversion to template:
lrwxrwxrwx 1 root root 0 Sep 25 18:26 /dev/zvol/rdsk/vMotion/base-124-disk-1@__base__ -> ../../../..//devices/pseudo/zfs@0:57,raw
After creating a linked clone:
lrwxrwxrwx 1 root root 0 Sep 25 18:27 /dev/zvol/rdsk/vMotion/vm-151-disk-1 -> ../../../..//devices/pseudo/zfs@0:58,raw
But instruction to create LUN from Proxmox GUI:
'/usr/bin/ssh -o 'BatchMode=yes' -i /etc/pve/priv/zfs/omnios_id_rsa root@omnios /usr/sbin/stmfadm create-lu -p 'wcd=false' -p 'guid=600144f5cb36f51b2b1ed38f3eb4a887' /dev/zvol/rdsk/vMotion/base-124-disk-1/vm-151-disk-1
So Proxmox GUI believes zvol is created in a subfolder 'vMotion/base-124-disk-1/vm-151-disk-1' which is clearly wrong since this is not possible.

 

[mir]

I forgot. The bug report, with a possible solution, can be found here: https://bugzilla.proxmox.com/show_bug.cgi?id=1122