Lxc zfs Filesystem name Bug in restoring zfs procedure

yena

Renowned Member
Nov 18, 2011
385
6
83
I have tested this:
if vol name is different than "subvol-......" the LXC container can't start:

rpool/RESTORED/vm-200-disk-1 -> starting error

zfs rename rpool/RESTORED/vm-200-disk-1 rpool/RESTORED/subvol-200-disk-1

rpool/RESTORED/subvol-200-disk-1 -> Start OK

( in both case i have the correct .conf file with correct rootfs: )

I hope this help someone that restore a disk with different name :-)
 
Hi,

I test this here and don't see this behavior!
Which version you are on?
Can you send the output of
Code:
 pveversion -v
 
Hi,

I test this here and don't see this behavior!
Which version you are on?
Can you send the output of
Code:
 pveversion -v

Proxmox version:

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.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.16-1-pve: 4.4.16-64
pve-kernel-4.2.2-1-pve: 4.2.2-16
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
 
How do you restore your containers?
 
Ok this is normal because we change the naming.
When you use vzdump it will handled by vzdump.

zfs send -v rpool/BACKUP/subvol-100-disk-1@rep_DbMeteoDaily_2016-09-06_15:27:59 | zfs receive rpool/RESTORED/vm-200-disk-1

zfs send -v rpool/BACKUP/subvol-100-disk-1@rep_DbMeteoDaily_2016-09-06_15:27:59 | zfs receive rpool/RESTORED/subvol-200-disk-1