[SOLVED] Backup failed - .conf.tmp File too large

fanatikz

New Member
Dec 20, 2024
2
0
1
Hi, I have a 2+ years working LXC container with node red and conbee stick mounted. And I cant do some backups anymore. couldn´t find anything about this issue. Any recommendation, what could be the reason for?

I recognized in the *.conf a strange entry after the TTY file creation. Not sure what caused this.

Details


VMIDNameStatusTimeSizeFilename
142VM 142err4s0 Bnull
Total running time: 4s

Logs

vzdump 142 --notes-template '{{guestname}}' --storage pbs --notification-mode auto --node server --mode snapshot --remove 0


142: 2024-12-20 15:54:56 INFO: Starting Backup of VM 142 (lxc)
142: 2024-12-20 15:54:56 INFO: status = running
142: 2024-12-20 15:55:00 ERROR: Backup of VM 142 failed - closing file '/etc/pve/nodes/server/lxc/142.conf.tmp.1775830' failed - File too large


eatures: nesting=1
hostname: node-red
memory: 2048
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=BC:24:11:5E:C6:77,ip=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-142-disk-0,size=8G
swap: 2048
unprivileged: 1
lxc.cgroup2.devices.allow: c 189:* rwm
lxc.mount.entry: usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2191817-if00 dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2191817-if00 none bind,optional,create=file
lxc.cgroup2.devices.allow: c 166:* rwm
lxc.mount.entry: /var/lib/lxc/141/devices/ttyACM0 dev/ttyACM0 none bind,optional,create=file ########fÃ^cÂ^cÃ^bÂ^cÃ^cÂ^bÃ^bÂ^cÃ^cÂ^cÃ^bÂ^bÃ^cÂ^bÃ^bÂ^cÃ^cÂ^cÃ^bÂ^cÃ^cÂ^bÃ^bÂ^bÃ^cÂ^cÃ^bÂ^bÃ^cÂ^bÃ^bÂ^cÃ>
 
Last edited:
Hi,
I recognized in the *.conf a strange entry after the TTY file creation. Not sure what caused this.
yeah, your config looks corrupt. How did you add this? Best would probably be to restore the config from a previous backup snapshot.
 
Seems this entry in config was miles long, i deleted it and the size shrinked from 5+GB to a few KB.
I created this config manually during the binding of my USB Device.
Backup is working again.