[SOLVED] Hard disk filling up during container backup

[bigun89]

I have a 40GB container, that while is being backed up and running at the same time, the VE HD space fills up and the job fails.

I have plenty of solid state storage that can be used as a staging area if needed, unsure how I can tell Proxmox to use another storage area for this stuff.

Also not super familiar with Proxmox, so be gentle with replies.

Here is the output of df:

root@homeproxmox:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
udev                   16G     0   16G   0% /dev
tmpfs                 3.2G  2.8M  3.2G   1% /run
/dev/mapper/pve-root   27G  3.8G   22G  15% /
tmpfs                  16G   46M   16G   1% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
/dev/sda2             511M  340K  511M   1% /boot/efi
/dev/sdb1             547G  188G  332G  37% /mnt/intflash
/dev/fuse             128M   24K  128M   1% /etc/pve
tmpfs                 3.2G     0  3.2G   0% /run/user/0

 

[fabian]

please post the output of 'pveversion -v' and the backup task log.

 

[bigun89]

root@homeproxmox:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.35-1-pve)
pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1)
pve-kernel-5.15: 7.2-3
pve-kernel-helper: 7.2-3
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.35-1-pve: 5.15.35-2
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-8
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-6
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.2-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.1.8-1
proxmox-backup-file-restore: 2.1.8-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-10
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-1
pve-qemu-kvm: 6.2.0-5
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

INFO: starting new backup job: vzdump 505 --node homeproxmox --mode snapshot --notes-template '{{guestname}}' --remove 0 --storage PBS
INFO: Starting Backup of VM 505 (lxc)
INFO: Backup started at 2022-05-15 23:48:20
INFO: status = running
INFO: CT Name: KF2-ct
INFO: including mount point rootfs ('/') in backup
INFO: mode failure - some volumes do not support snapshots
INFO: trying 'suspend' mode instead
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: CT Name: KF2-ct
INFO: including mount point rootfs ('/') in backup
INFO: starting first sync /proc/3043454/root/ to /var/tmp/vzdumptmp3045762_505
ERROR: Backup of VM 505 failed - command 'rsync --stats -h -X -A --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' /proc/3043454/root//./ /var/tmp/vzdumptmp3045762_505' failed: exit code 11
INFO: Failed at 2022-05-15 23:53:30
INFO: Backup job finished with errors
TASK ERROR: job errors

 

[fabian]

you have two options:
- ensure you can use 'snapshot' mode (only suspend mode requires a temporary copy)
- set 'tmpdir' in /etc/vzdump.conf (on all nodes if clustered)

 

[bigun89]

Yup, plopped in the path to more usable temp storage into vzdump.conf and it finished. Thank you for the help!