Error backing up LXC container

[Matthias182]

Hi,

I do have a problem with a newly created LXC container when backing up to my NAS.

I do get the error:

ERROR: Backup of VM 102 failed - command 'rsync --stats -h --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' '--exclude=/mnt/rackstation' /proc/4002196/root//./ /mnt/pve/Rackstation/dump/vzdump-lxc-102-2024_05_23-17_16_41.tmp' failed: exit code 23

When I execute the same command outside the GUI, I do see a lot of errors from trying to change object owner:

rsync: [receiver] chown "/mnt/pve/Rackstation/dump/vzdump-lxc-102-2024_05_23-07_45_33.tmp/var/spool/postfix/lib/x86_64-linux-gnu/.libnss_compat.so.2.NsV5EI" failed: Invalid argument (22)
rsync: [receiver] chown "/mnt/pve/Rackstation/dump/vzdump-lxc-102-2024_05_23-07_45_33.tmp/var/spool/postfix/lib/x86_64-linux-gnu/.libnss_dns.so.2.q6cB5d" failed: Invalid argument (22)
rsync: [receiver] chown "/mnt/pve/Rackstation/dump/vzdump-lxc-102-2024_05_23-07_45_33.tmp/var/spool/postfix/lib/x86_64-linux-gnu/.libnss_files.so.2.JNd36M" failed: Invalid argument (22)
rsync: [receiver] chown "/mnt/pve/Rackstation/dump/vzdump-lxc-102-2024_05_23-07_45_33.tmp/var/spool/postfix/lib/x86_64-linux-gnu/.libnss_hesiod.so.2.zvEGVU" failed: Invalid argument (22)
rsync: [receiver] chown "/mnt/pve/Rackstation/dump/vzdump-lxc-102-2024_05_23-07_45_33.tmp/var/spool/postfix/lib/x86_64-linux-gnu/.libnss_systemd.so.2.GBUKez" failed: Invalid argument (22)
rsync: [receiver] chown "/mnt/pve/Rackstation/dump/vzdump-lxc-102-2024_05_23-07_45_33.tmp/var/spool/postfix/lib/x86_64-linux-gnu/.libresolv.so.2.gX1RWm" failed: Invalid argument (22)
rsync: [receiver] chown "/mnt/pve/Rackstation/dump/vzdump-lxc-102-2024_05_23-07_45_33.tmp/var/spool/postfix/pid/.master.pid.PSVHA7" failed: Invalid argument (22)

The NAS is connected to Proxmox using NFS:

dir: local
    path /var/lib/vz
    content images,rootdir,vztmpl
    shared 0

lvmthin: local-lvm
    thinpool data
    vgname pve
    content images,rootdir

nfs: Rackstation
    export /volume1/Datensicherung
    path /mnt/pve/Rackstation
    server xxx
    content rootdir,backup,snippets,vztmpl,images,iso
    prune-backups keep-all=1

Does anybody have an idea what the reason could be?


Thanks,
Matthias

 

[Screemy]

Hi, there is any news?

I check ls -lha on mount point of NFS but see strange ownership

 

[ktfcaptain]

Hey, I'm no expert with proxmox in the least, but I just had the same/similar issue that actually locked up the local PC I was logged in from and everything until I pulled power....

I think it was simply because I left the default options in-place for it to take a Snapshot instead of Stop/Suspend. Changed "Mode" to Stop and it ran perfect.

 

[Malalajan]

Hi, I believe I had the same problem as you, my container backed up fine until I removed it and restored to a new container number (I try to align them to their IP addresses). After which point my container would not back up as a snapshot with the same errors as you have. Stopping the container for backup seemed to work fine though.
I believe the issues was with the config file '/etc/pve/lxc/xxx.conf' as this holds the incremental changes from snapshots. I removed this manually and restored the container and it is fine now.
Note that when I deleted this file, the container disappeared from the Proxmox interface but still appeared to be running, I probably should have stopped or removed first, however the restore resolved this.

 

[rh8dohgnoidr]

Just came here to say that I had the same problem after moving a container to a different disk and Malalajans post worked out perfectly!