[SOLVED] lxc restore fail

R

RobFantini

Famous Member
May 24, 2012
2,042
110
133
Boston,Mass
i was testing restore.
Code: 
/dev/rbd8
mke2fs 1.44.5 (15-Dec-2018)
Discarding device blocks:    4096/1048576               done                        
Creating filesystem with 1048576 4k blocks and 262144 inodes
Filesystem UUID: 62ccd035-2693-4156-b9f2-49621aa7d26c
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables:  0/32     done                        
Writing inode tables:  0/32     done                        
Creating journal (16384 blocks): done
Multiple mount protection is enabled with update interval 5 seconds.
Writing superblocks and filesystem accounting information:  0/32     done

thread 'main' panicked at 'not yet implemented: apply flags!', src/pxar/metadata.rs:86:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Removing image: 1% complete...
Removing image: 2% complete...
Removing image: 3% complete...
Removing image: 4% complete...
..
TASK ERROR: unable to restore CT 99932 - command '/usr/bin/proxmox-backup-client restore '--crypt-mode=none' ct/126/2020-07-11T22:49:05Z root.pxar /var/lib/lxc/99932/rootfs --allow-existing-dirs --repository pbs-user@pbs@10.1.10.80:backups' failed: exit code 101

here is output of show configuration:
Code: 
arch: amd64
cores: 2
cpulimit: 1
features: nesting=1
hostname: ona
memory: 2048
net0: name=eth0,bridge=vmbr0,gw=10.1.3.1,hwaddr=32:4B:90:84:9E:50,ip=10.1.3.60/24,tag=3,type=veth
net1: name=eth1,bridge=vmbr0,hwaddr=EA:7B:35:A1:B0:C3,ip=10.1.3.61/24,tag=3,type=veth
onboot: 1
ostype: debian
rootfs: nvme-4tb:vm-126-disk-0,size=4G
swap: 512
lxc.apparmor.profile: generated
lxc.apparmor.allow_nesting: 1
 
version at pve host:
Code: 
>>> pveversion -v

proxmox-ve: 6.2-1 (running kernel: 5.4.44-2-pve)
pve-manager: 6.2-9 (running version: 6.2-9/4d363c5b)
pve-kernel-5.4: 6.2-4
pve-kernel-helper: 6.2-4
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.4.44-1-pve: 5.4.44-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
ceph: 14.2.9-pve1
ceph-fuse: 14.2.9-pve1
corosync: 3.0.4-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.16-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-5
libpve-guest-common-perl: 3.0-11
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-3
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-9
pve-cluster: 6.1-8
pve-container: 3.1-10
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-9
pve-xtermjs: 4.3.0-1
pve-zsync: 2.0-3
qemu-server: 6.2-8
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1
 
RobFantini said:
thread 'main' panicked at 'not yet implemented: apply flags!', src/pxar/metadata.rs:86:9 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Click to expand...

Yeah, there's something missing there with file flags on restore like "immutable" - we'll look into it.
 
Was a leftover `todo!()` entry in the code I somehow missed, should work with the next proxmox-backup-client update (0.8.7-1).
 
You must log in or register to reply here.
Top Bottom