LXC restore ends in error

[Cronus89]

I have restored 2 other VM's and 1 other CT, which are large and went fine. However this one small lxc container that is 1.57GB will not restore it says ran out of disk space

recovering backed-up configuration from 'pbs:backup/ct/104/2021-05-10T01:14:32Z'
  Logical volume "vm-104-disk-0" created.
Creating filesystem with 8388608 4k blocks and 2097152 inodes
Filesystem UUID: b96b56da-e66c-4283-bd62-ad471499a851
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
    4096000, 7962624
restoring 'pbs:backup/ct/104/2021-05-10T01:14:32Z' now..
Error: error extracting archive - error at entry "3481fff742ac3c5e1d42c46ba5e2190fa956c1a135809dffcd3b5b2fab1749fa-primary.xml.gz": failed to apply extended attributes: No space left on device (os error 28)
  Logical volume "vm-104-disk-0" successfully removed
TASK ERROR: unable to restore CT 104 - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client restore '--crypt-mode=none' ct/104/2021-05-10T01:14:32Z root.pxar /var/lib/lxc/104/rootfs --allow-existing-dirs --repository renx_colo@pbs@209.141.49.249:slab-datastore' failed: exit code 255

Filesystem            Size  Used Avail Use% Mounted on
udev                  7.8G     0  7.8G   0% /dev
tmpfs                 1.6G   41M  1.6G   3% /run
/dev/mapper/pve-root   94G  3.4G   86G   4% /
tmpfs                 7.9G   43M  7.8G   1% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
tmpfs                 7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/fuse              30M   16K   30M   1% /etc/pve
tmpfs                 1.6G     0  1.6G   0% /run/user/0

Filesystem            Size  Used Avail Use% Mounted on
udev                  7.8G     0  7.8G   0% /dev
tmpfs                 1.6G   41M  1.6G   3% /run
/dev/mapper/pve-root   94G  3.4G   86G   4% /
tmpfs                 7.9G   43M  7.8G   1% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
tmpfs                 7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/fuse              30M   16K   30M   1% /etc/pve
tmpfs                 1.6G     0  1.6G   0% /run/user/0

 

[dcsapak]

can you post the versions of your systems? 'pveversion -v'

my guess is that you had large sparse files in the backup? (with a current proxmox-backup-client this will be restored sparsely)

edit: or your original storage was one where it could compress the filesystem (like zfs) ?

 

[Cronus89]

Original was zfs, however the VM was tiny. just a basic headless fedora with freeipa installed. its a 1.57GB backup total of data.

Below is from pve

root@prox:~# pveversion -v
proxmox-ve: 6.4-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.4-6 (running version: 6.4-6/be2fa32c)
pve-kernel-5.4: 6.4-2
pve-kernel-helper: 6.4-2
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.4-1
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-2
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.6-2
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-4
pve-cluster: 6.4-1
pve-container: 3.3-5
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-3
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

 

[dcsapak]

i just saw:

Error: error extracting archive - error at entry "3481fff742ac3c5e1d42c46ba5e2190fa956c1a135809dffcd3b5b2fab1749fa-primary.xml.gz": failed to apply extended attributes: No space left on device (os error 28)

it seems that this file has extended attributes that are too big for the new filesystem... (each filesystem has its own limits about extended attributes)

 

[Cronus89]

Anyway to see what attributes wont work? Can something be done to recover this still?

 

[dcsapak]

Anyway to see what attributes wont work? Can something be done to recover this still?

you can either
restore the container to a zfs storage (that should be able to hold the xattrs) or
download the 'pxar' archive manually (e.g. via the webinterface or 'proxmox-backup-client'; see the man page for details) and restore it with 'pxar extract --no-xattrs'