Restore to ZFS

Matus

Renowned Member
Mar 31, 2017
28
0
66
67
Hi,

I tried to restore backup to local ZFS storage and process finished with error 144:

>pct restore 104 /var/lib/vz/dump/vzdump-lxc-100-2017_03_24-15_14_36.tar.lzo -storage local
Formatting '/var/lib/vz/images/104/vm-104-disk-2.raw', fmt=raw size=21474836480
mke2fs 1.42.12 (29-Aug-2014)
Discarding device blocks: done
Creating filesystem with 5242880 4k blocks and 1310720 inodes
Filesystem UUID: 36f6370f-db56-43d1-8426-721d0271fe3d
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information:
Warning, had trouble writing out superblocks.TASK ERROR: command 'mkfs.ext4 -O mmp -E 'root_owner=0:0' /var/lib/vz/images/104/vm-104-disk-2.raw' failed: exit code 144


Could you help me?
 
please post
Code:
pveversion -v

and the content of /etc/pve/storage.cfg
 
proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80


dir: local
path /var/lib/vz
maxfiles 100
shared 1
content vztmpl,backup,images,rootdir,iso

zfspool: local-zfs
pool rpool/data
nodes alto
sparse 0
content images,rootdir
 
1. please upgrade to a more current version
2. you are not restoring to ZFS, but to your local directory storage
3. you marked your local directory storage as "shared", which is almost certainly wrong