PVE beta 9 - cannot restore LXC from PBS

K

Kingneutron

Renowned Member
Feb 21, 2024
1,066
383
88
github.com
Header
Proxmox
Virtual Environment 9.0.0~8
BETA
Storage 'qotom-pbs-bkp-for-beelink-vms-25g' on node 'pvefry4'
Search:
Logs
()
recovering backed-up configuration from 'qotom-pbs-bkp-for-beelink-vms-25g:backup/ct/110/2025-07-17T04:33:50Z'
Use of uninitialized value $fmt in string eq at /usr/share/perl5/PVE/Storage/LVMPlugin.pm line 517.
WARNING: You have not turned on protection against thin pools running out of space.
WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full.
Logical volume "vm-104-disk-0" created.
WARNING: Sum of all thin volume sizes (<93.01 GiB) exceeds the size of thin pool pve/data and the amount of free space in volume group (1.00 GiB).
Logical volume pve/vm-104-disk-0 changed.
Creating filesystem with 2097152 4k blocks and 524288 inodes
Filesystem UUID: 3b099903-7703-41e5-95af-6bbcdba3c7a0
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
restoring 'qotom-pbs-bkp-for-beelink-vms-25g:backup/ct/110/2025-07-17T04:33:50Z' now..
Error: error extracting archive - encountered unexpected error during extraction: error at entry "bzcat": failed to extract hardlink: EINVAL: Invalid argument
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/110/2025-07-17T04:33:50Z root.pxar /var/lib/lxc/104/rootfs --allow-existing-dirs --repository root@pam@qotom-pbs-bkp-for-beelink-vms-25g:datastore1-xfs-400' failed: exit code 255

=====

Proxmox 8.3.2 upgraded to 8.4.5, rebooted, upgraded in-place to Beta 9, rebooted

PBS version is 3.4.1; NOTE: updates pending on PBS, will attempt upgrade

Cannot restore small LXC from PBS - gets above error

LXC config: 1x vcpu, 64MB RAM, 8GB vdisk
 
Think I figured it out, the intended "storage destination" (zfs pool) was a multi-use Directory that did not have "disk image" selected.
Restoring to the ZFS pool itself from PBS works OK, and I have since fixed the lack of "disk image" on the multiuse dir
 
Nope, still not fixed - trying to restore LXC to beta 9 from PBS still failing:

Header
Proxmox
Virtual Environment 9.0.0~8
BETA
Storage 'qotom-pbs-bkp-for-beelink-vms-25g' on node 'pvefry4'
Search:
Logs
()
recovering backed-up configuration from 'qotom-pbs-bkp-for-beelink-vms-25g:backup/ct/125/2025-07-18T04:44:54Z'
Formatting '/mnt/fryxfs/images/107/vm-107-disk-0.raw', fmt=raw size=17179869184 preallocation=off
Creating filesystem with 4194304 4k blocks and 1048576 inodes
Filesystem UUID: 69d34349-0348-432f-be10-3f0cff57b65e
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
restoring 'qotom-pbs-bkp-for-beelink-vms-25g:backup/ct/125/2025-07-18T04:44:54Z' now..
Error: error extracting archive - encountered unexpected error during extraction: error at entry "bzcat": failed to extract hardlink: EINVAL: Invalid argument
TASK ERROR: unable to restore CT 107 - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client restore '--crypt-mode=none' ct/125/2025-07-18T04:44:54Z root.pxar /var/lib/lxc/107/rootfs --allow-existing-dirs --repository root@pam@qotom-pbs-bkp-for-beelink-vms-25g:datastore1-xfs-400' failed: exit code 255
 
Hi,
regarding the following error
Kingneutron said:
Use of uninitialized value $fmt in string eq at /usr/share/perl5/PVE/Storage/LVMPlugin.pm line 517.
Click to expand...
please share your storage configuration on the PVE host cat /etc/pve/storage.cfg as well as the container configuration as stored in the backup, which you obtain by selecting the snapshot and click the Show Configuration button.

Regarding the extraction issue itself
Kingneutron said:
Error: error extracting archive - encountered unexpected error during extraction: error at entry "bzcat": failed to extract hardlink: EINVAL: Invalid argument
Click to expand...
does the issue persist independent of backing storage of the restore target? E.g. zfs and lvm-thin? Can you maybe also verify that the same snapshots restores without issues on a PVE 8.4 installation? The error would indicate that the extraction fails on hardlink creation, there were however no recent changes to this codepath for the proxmox-backup-client, so this might be a pre-existing issue unrelated to the PVE 9 beta.
Also, what change detection mode was used to create this backup snapshot? Could you post the backup task log as well?
 
  • Like
Reactions: Johannes S
The second issue is a regression in PBS 4 beta client, I got a patch in progress - we pass linkat a flag for not following symlinks, but that is the default behavior so it only has a flag for enabling the opposite behavior. In PBS 3 that was seemingly filtered out, now it causes an EINVAL.
 
  • Like
Reactions: Chris and Johannes S
So the fix played out well and as it's very targeted and the cause also clear and reproducible, we build and already uploaded a new proxmox-backup-client package in version 4.0.3-1 including a fix to the pve-test repo.

After upgrading to that version the restore should work again - thanks for your report!
 
  • Like
Reactions: Chris and Johannes S
You must log in or register to reply here.
Top Bottom