exclude-path from LXC backup (my) issue

[Vittorio]

Hi all

I'm getting a no space left on device while doing a scheduled backup defined in datacenter

This is the log

INFO: starting new backup job: vzdump 102 --exclude-path '/media/frigate/recordings/ /media/frigate/clips/ /dev/mapper/ /dev/fuse/ /dev/shm/ /run/ /var/lib/docker/' --quiet 1 --mailto woody4165@gmail.com --storage EXT_USB --notes-template '{{guestname}}' --mailnotification failure --mode stop --compress zstd --prune-backups 'keep-last=2' --node new
INFO: Starting Backup of VM 102 (lxc)
INFO: Backup started at 2024-02-17 05:00:04
INFO: status = running
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: CT Name: docker-frigate
INFO: including mount point rootfs ('/') in backup
INFO: stopping virtual guest
INFO: creating vzdump archive '/media/ext_usb/backup/dump/vzdump-lxc-102-2024_02_17-05_00_04.tar.zst'
INFO: zstd: error 70 : Write error : cannot write block : No space left on device
INFO: restarting vm
explicitly configured lxc.apparmor.profile overrides the following settings: features:nesting
INFO: guest is online again after 603 seconds
ERROR: Backup of VM 102 failed - command 'set -o pipefail && tar cpf - --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' --one-file-system '--warning=no-file-ignored' '--directory=/media/ext_usb/backup/dump/vzdump-lxc-102-2024_02_17-05_00_04.tmp' ./etc/vzdump/pct.conf ./etc/vzdump/pct.fw '--directory=/mnt/vzsnap0' --no-anchored '--exclude=lost+found' --anchored '--exclude=./media/frigate/recordings/ /media/frigate/clips/ /dev/mapper/ /dev/fuse/ /dev/shm/ /run/ /var/lib/docker/' '--exclude=./tmp/?*' '--exclude=./var/tmp/?*' '--exclude=./var/run/?*.pid' ./ | zstd '--threads=1' >/media/ext_usb/backup/dump/vzdump-lxc-102-2024_02_17-05_00_04.tar.dat' failed: exit code 70
INFO: Failed at 2024-02-17 05:10:10
INFO: Backup job finished with errors
INFO: notified via target `<woody4165@gmail.com>`
TASK ERROR: job errors

And this is the /etc/vzdump.conf

# vzdump default settings


#tmpdir: DIR
#dumpdir: DIR
#storage: STORAGE_ID
#mode: snapshot|suspend|stop
#bwlimit: KBPS
#performance: max-workers=N
#ionice: PRI
#lockwait: MINUTES
#stopwait: MINUTES
#stdexcludes: BOOLEAN
#mailto: ADDRESSLIST
#prune-backups: keep-INTERVAL=N[,...]
#script: FILENAME
#exclude-path: PATHLIST
#pigz: N
#notes-template: {{guestname}}
exclude-path: "/media/frigate/recordings/" "/media/frigate/clips/" "/var/lib/docker/" "/dev/mapper/" "/dev/fuse/" "/dev/shm/" "/run/"

pveversion -v is

proxmox-ve: 8.1.0 (running kernel: 5.15.126-1-pve)
pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79)
proxmox-kernel-helper: 8.1.0
pve-kernel-5.15: 7.4-9
proxmox-kernel-6.5: 6.5.11-8
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
pve-kernel-5.15.131-2-pve: 5.15.131-3
pve-kernel-5.15.131-1-pve: 5.15.131-2
pve-kernel-5.15.126-1-pve: 5.15.126-1
pve-kernel-5.15.116-1-pve: 5.15.116-1
pve-kernel-5.15.111-1-pve: 5.15.111-1
pve-kernel-5.15.108-1-pve: 5.15.108-2
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.107-1-pve: 5.15.107-1
pve-kernel-5.15.104-1-pve: 5.15.104-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
ceph-fuse: 17.2.7-pve2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.1
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.4-1
proxmox-backup-file-restore: 3.1.4-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.4
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-3
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.2.0
pve-qemu-kvm: 8.1.5-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve1

Checking in webui proxmox the disk is 120GB and this is the actual usage



Also doing df -h reports that /dev/sdc1 has 50GB available

root@new:/media/ext_usb# df -h
Filesystem            Size  Used Avail Use% Mounted on
udev                  3.8G     0  3.8G   0% /dev
tmpfs                 779M  1.1M  778M   1% /run
/dev/mapper/pve-root   29G   22G  5.6G  80% /
tmpfs                 3.9G   37M  3.8G   1% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
/dev/sdc1             102G   48G   50G  49% /media/ext_usb
/dev/sda2             511M  328K  511M   1% /boot/efi
/dev/fuse             128M   28K  128M   1% /etc/pve
tmpfs                 779M     0  779M   0% /run/user/0

If the backup does not include the folder specified in exclude-path it shoud be around 1GB

I don't remember if there is also a conf file specific for an LXC backup and not generic like vzdump.conf

What I can check?

Thanks

 

[Moayad]

Hi,

/dev/mapper/pve-root 29G 22G 5.6G 80% /

You have to have enough space on the pve-root, in this case I would try to change the `#tmpdir: DIR` in the vzdump.conf.