> Did you create a zfs type storage on the GUI?
* HDD: /var/lib/vz/ is zfs partition. it was created by Installer (ZFS RAID0).
* SSD: used to that's cache(L2ARC) and log(ZIL).
It occured restore from openvz dump,
and create a lxc container from GUI.
When I created a zfs type storage on the GUI, only "KVM Image" could handle.
I founded add zfs's directory path can handle all type of archives.
## error message.
~~~
root@:/var/lib/vz/dump# pct restore 307 `pwd`/vzdump-openvz-307-2015_09_13-07_52_37.tar
Formatting '/var/lib/vz/images/307/vm-307-disk-1.raw', fmt=raw size=4294967296
mke2fs 1.42.12 (29-Aug-2014)
Discarding device blocks: done
Creating filesystem with 1048576 4k blocks and 262144 inodes
Filesystem UUID: 21d3724c-f71e-4a8e-b123-fba4e7a4a76e
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736
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 /var/lib/vz/images/307/vm-307-disk-1.raw' failed: exit code 144
~~~