Hi,
I'm trying to restore the lZO file but I get the following error.
Would cloud be the reason for this?
Thanks
I'm trying to restore the lZO file but I get the following error.
Code:
Using default stripesize 64.00 KiB.
For thin pool auto extension activation/thin_pool_autoextend_threshold should be below 100.
Logical volume "vm-107-disk-1" created.
WARNING: Sum of all thin volume sizes (1.64 TiB) exceeds the size of thin pool pve/data and the size of whole volume group (558.48 GiB)!
mke2fs 1.43.4 (31-Jan-2017)
Discarding device blocks: 4096/15728640 done
Creating filesystem with 15728640 4k blocks and 3932160 inodes
Filesystem UUID: 6f14d148-635f-4d7a-a895-0c321507ec76
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: 0/480 done
Writing inode tables: 0/480 done
Creating journal (65536 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information: 0/480 done
extracting archive '/Backups/dump/vzdump-lxc-107-2018_04_25-00_00_53.tar.lzo'
tar: ./var/spool/postfix/dev/urandom: Cannot mknod: Operation not permitted
tar: ./var/spool/postfix/dev/random: Cannot mknod: Operation not permitted
Total bytes read: 7207045120 (6.8GiB, 87MiB/s)
tar: Exiting with failure status due to previous errors
Logical volume "vm-107-disk-1" successfully removed
TASK ERROR: command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar xpf - --lzop --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' -C /var/lib/lxc/107/rootfs --skip-old-files --anchored --exclude './dev/*'' failed: exit code 2Would cloud be the reason for this?
Thanks