[SOLVED] Backup Erroneously Reporting Insufficient Space.
- Thread starter dCipher
- Start date
Hi. This might be a blind shot, but I seem to remember a similar issue when the reason was the space in a temporary directory, not on the destination device.
Maybe you'll be able to "google" for a similar thread...
edit: Also fleecing rings some bell. My memories may be wrong of course.
Maybe you'll be able to "google" for a similar thread...
edit: Also fleecing rings some bell. My memories may be wrong of course.
Last edited:
Maybe this is a hint: https://forum.proxmox.com/threads/backup-job-error-no-space-left-on-device.160098/
Main2TB does not support snapshots so you need temporary space to back it up unless you use the stop mode.If you can, wipe and re-create it as ZFS or LVM-Thin. Otherwise you need to use a different mode or set the vzdump
tmpdir to some place where you have enough space.
Last edited:
I tried the stop mode but I get the same error. So I guess I need to move my tmpdir because local only has 120Gb capacity. The Main2TB drive has about a terabyte of free space perhaps I could move it there. Being new to Linux I am not sure the best way to move the tmpdir. Do I have to create a directory on the Main2TB drive first and then update the /etc/vsdump.conf file or can I just change the vsdump.conf file and it will then create the new directory?
Hmm. I wonder why this doesn't work in stop mode. Maybe I missed something? Can you share the stop mode's backup task log?
The
There's a way to create a thin volume to store data but you have pure LVM and likely no unallocated space for creating a thick volume.
Can you also share
The
tmpdir path has to exist. The issue is which path do we use? You can't directly store files on LVM.There's a way to create a thin volume to store data but you have pure LVM and likely no unallocated space for creating a thick volume.
Can you also share
lsblk -o+FSTYPE,MODEL, pvs and lvs? I still recommend to wipe and re-create this storage if possible!
Code:
root@minipc:~# lsblk -o+FSTYPE,MODEL, pvs
lsblk: unknown column: MODEL,
root@minipc:~# lsblk -o+FSTYPE,MODEL
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS FSTYPE MODEL
sda 8:0 0 1.8T 0 disk Samsung SSD 990 PRO 2TB
└─sda1 8:1 0 1.8T 0 part /media/simon/backup ext4
nvme0n1 259:0 0 1.8T 0 disk LVM2_member Samsung SSD 990 PRO 2TB
├─Main2TB-vm--101--disk--0 252:6 0 500G 0 lvm
└─Main2TB-vm--102--disk--0 252:9 0 200G 0 lvm
nvme1n1 259:1 0 953.9G 0 disk KINGSTON OM8TAP41024K1-A00
├─nvme1n1p1 259:2 0 1007K 0 part
├─nvme1n1p2 259:3 0 1G 0 part /boot/efi vfat
└─nvme1n1p3 259:4 0 952G 0 part LVM2_member
├─pve-swap 252:0 0 8G 0 lvm [SWAP] swap
├─pve-root 252:1 0 96G 0 lvm / ext4
├─pve-data_tmeta 252:2 0 8.3G 0 lvm
│ └─pve-data-tpool 252:4 0 815.4G 0 lvm
│ ├─pve-data 252:5 0 815.4G 1 lvm
│ ├─pve-vm--101--disk--0 252:7 0 4M 0 lvm
│ └─pve-vm--101--disk--2 252:8 0 4M 0 lvm
└─pve-data_tdata 252:3 0 815.4G 0 lvm
└─pve-data-tpool 252:4 0 815.4G 0 lvm
├─pve-data 252:5 0 815.4G 1 lvm
├─pve-vm--101--disk--0 252:7 0 4M 0 lvm
└─pve-vm--101--disk--2 252:8 0 4M 0 lvm
Code:
root@minipc:~# pvs
PV VG Fmt Attr PSize PFree
/dev/nvme0n1 Main2TB lvm2 a-- <1.82t <1.04t
/dev/nvme1n1p3 pve lvm2 a-- <952.00g 16.00g
root@minipc:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
vm-100-disk-0 Main2TB -wi------- 100.00g
vm-101-disk-0 Main2TB -wi-ao---- 500.00g
vm-102-disk-0 Main2TB -wi-ao---- 200.00g
data pve twi-aotz-- <815.36g 4.41 0.38
root pve -wi-ao---- 96.00g
swap pve -wi-ao---- 8.00g
vm-101-disk-0 pve Vwi-aotz-- 4.00m data 14.06
vm-101-disk-2 pve Vwi-aotz-- 4.00m data 1.56
vm-102-disk-0 pve Vwi---tz-- 200.00g data
root@minipc:~#What about the Backup Log? You have 1T of unallocated space on
We could also use
Try something like this, then start a new Backup
You can investigate the storage with something like this
Main2TB's PV we could use for this. Just feels like a big waste though.We could also use
/media/simon/backup which would be my recommendation as it's infinitely simpler.Try something like this, then start a new Backup
Bash:
mkdir -p /media/simon/backup/vzdumptmp
echo "tmpdir: /media/simon/backup/vzdumptmp" >> /etc/vzdump.cfg
Bash:
apt install -y gdu
gdu /media/
Last edited:
Is this the USB-attached drive?:
If it is, it appears to be mounted at
If this is another drive, then please show
Also show output for
Code:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS FSTYPE MODEL
sda 8:0 0 1.8T 0 disk Samsung SSD 990 PRO 2TB
└─sda1 8:1 0 1.8T 0 part /media/simon/backup ext4/media/simon/backup but not at path /mnt/usb-backup as your above storage.cfg output would suggest.If this is another drive, then please show
lsblk output, including the USB-attached drive.Also show output for
df -h.Here is the backup log that I forgot to add.
Code:
INFO: starting new backup job: vzdump 101 102 --notes-template '{{guestname}}' --compress zstd --mode stop --prune-backups 'keep-last=2' --storage Backup --all 0 --node minipc --notification-mode notification-system --fleecing 0
INFO: Starting Backup of VM 101 (qemu)
INFO: Backup started at 2025-12-08 10:40:45
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: WinLTSC
INFO: include disk 'scsi0' 'Main2TB:vm-101-disk-0' 500G
INFO: include disk 'efidisk0' 'local-lvm:vm-101-disk-0' 4M
INFO: include disk 'tpmstate0' 'local-lvm:vm-101-disk-2' 4M
INFO: creating vzdump archive '/mnt/usb-backup/dump/vzdump-qemu-101-2025_12_08-10_40_45.vma.zst'
INFO: starting kvm to execute backup task
EFI disk without 'ms-cert=2023' option, suggesting that the Microsoft UEFI 2023 certificate is not enrolled yet. The UEFI 2011 certificate expires in June 2026!
While the VM is shut down, run 'qm enroll-efi-keys 101' to enroll it.
If the VM uses BitLocker, run the following command inside Windows Powershell:
manage-bde -protectors -disable <drive>
for each drive with BitLocker (for example, <drive> could be 'C:').
swtpm_setup: Not overwriting existing state file.
INFO: attaching TPM drive to QEMU for backup
INFO: started backup task 'fe93ad51-3b3b-4e77-b45f-2e02350a6689'
INFO: 0% (4.7 GiB of 500.0 GiB) in 3s, read: 1.6 GiB/s, write: 1.5 GiB/s
INFO: 1% (9.4 GiB of 500.0 GiB) in 6s, read: 1.6 GiB/s, write: 1.5 GiB/s
INFO: 2% (14.1 GiB of 500.0 GiB) in 9s, read: 1.6 GiB/s, write: 1.5 GiB/s
INFO: 4% (20.1 GiB of 500.0 GiB) in 12s, read: 2.0 GiB/s, write: 1.9 GiB/s
INFO: 5% (26.9 GiB of 500.0 GiB) in 16s, read: 1.7 GiB/s, write: 1.6 GiB/s
INFO: 6% (30.2 GiB of 500.0 GiB) in 20s, read: 855.5 MiB/s, write: 824.2 MiB/s
INFO: 7% (35.2 GiB of 500.0 GiB) in 24s, read: 1.2 GiB/s, write: 1.2 GiB/s
zstd: error 70 : Write error : cannot write block : No space left on device
INFO: 8% (40.1 GiB of 500.0 GiB) in 28s, read: 1.2 GiB/s, write: 962.5 MiB/s
ERROR: vma_queue_write: write error - Broken pipe
INFO: aborting backup job
INFO: stopping kvm after backup task
trying to acquire lock...
OK
ERROR: Backup of VM 101 failed - vma_queue_write: write error - Broken pipe
INFO: Failed at 2025-12-08 10:41:17
INFO: Starting Backup of VM 102 (qemu)
INFO: Backup started at 2025-12-08 10:41:17
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: LinuxMint
INFO: include disk 'scsi0' 'Main2TB:vm-102-disk-0' 200G
INFO: skip unused drive 'local-lvm:vm-102-disk-0' (not included into backup)
INFO: creating vzdump archive '/mnt/usb-backup/dump/vzdump-qemu-102-2025_12_08-10_41_17.vma.zst'
INFO: starting kvm to execute backup task
INFO: started backup task 'facdad51-deaf-4615-afb1-af99d6cd4799'
INFO: 2% (4.1 GiB of 200.0 GiB) in 3s, read: 1.4 GiB/s, write: 411.2 MiB/s
INFO: 3% (6.4 GiB of 200.0 GiB) in 7s, read: 597.2 MiB/s, write: 538.1 MiB/s
INFO: 4% (8.7 GiB of 200.0 GiB) in 10s, read: 768.5 MiB/s, write: 660.7 MiB/s
INFO: 5% (10.3 GiB of 200.0 GiB) in 15s, read: 336.4 MiB/s, write: 333.1 MiB/s
INFO: 6% (12.6 GiB of 200.0 GiB) in 19s, read: 583.6 MiB/s, write: 457.5 MiB/s
INFO: 7% (14.8 GiB of 200.0 GiB) in 22s, read: 766.1 MiB/s, write: 600.3 MiB/s
INFO: 8% (16.7 GiB of 200.0 GiB) in 25s, read: 623.5 MiB/s, write: 575.8 MiB/s
INFO: 9% (19.5 GiB of 200.0 GiB) in 28s, read: 969.1 MiB/s, write: 680.6 MiB/s
INFO: 10% (21.0 GiB of 200.0 GiB) in 31s, read: 499.0 MiB/s, write: 402.4 MiB/s
INFO: 18% (36.8 GiB of 200.0 GiB) in 34s, read: 5.3 GiB/s, write: 99.7 MiB/s
INFO: 27% (55.8 GiB of 200.0 GiB) in 37s, read: 6.3 GiB/s, write: 57.3 KiB/s
INFO: 31% (62.3 GiB of 200.0 GiB) in 40s, read: 2.2 GiB/s, write: 493.3 MiB/s
INFO: 32% (64.7 GiB of 200.0 GiB) in 43s, read: 797.5 MiB/s, write: 682.2 MiB/s
INFO: 37% (76.0 GiB of 200.0 GiB) in 46s, read: 3.8 GiB/s, write: 328.7 MiB/s
INFO: 47% (94.9 GiB of 200.0 GiB) in 49s, read: 6.3 GiB/s, write: 88.0 KiB/s
INFO: 52% (105.3 GiB of 200.0 GiB) in 52s, read: 3.5 GiB/s, write: 541.6 MiB/s
INFO: 53% (107.5 GiB of 200.0 GiB) in 55s, read: 737.1 MiB/s, write: 567.5 MiB/s
INFO: 54% (109.5 GiB of 200.0 GiB) in 58s, read: 688.8 MiB/s, write: 560.0 MiB/s
INFO: 55% (112.0 GiB of 200.0 GiB) in 1m 1s, read: 845.8 MiB/s, write: 586.2 MiB/s
INFO: 57% (114.1 GiB of 200.0 GiB) in 1m 4s, read: 727.4 MiB/s, write: 682.5 MiB/s
INFO: 58% (116.4 GiB of 200.0 GiB) in 1m 7s, read: 784.2 MiB/s, write: 616.0 MiB/s
INFO: 59% (118.6 GiB of 200.0 GiB) in 1m 10s, read: 773.3 MiB/s, write: 675.3 MiB/s
INFO: 60% (121.4 GiB of 200.0 GiB) in 1m 13s, read: 940.1 MiB/s, write: 741.2 MiB/s
INFO: 61% (123.6 GiB of 200.0 GiB) in 1m 16s, read: 755.2 MiB/s, write: 711.5 MiB/s
INFO: 63% (126.3 GiB of 200.0 GiB) in 1m 19s, read: 932.8 MiB/s, write: 780.9 MiB/s
INFO: 66% (132.8 GiB of 200.0 GiB) in 1m 22s, read: 2.1 GiB/s, write: 456.0 MiB/s
INFO: 68% (137.1 GiB of 200.0 GiB) in 1m 25s, read: 1.4 GiB/s, write: 618.0 MiB/s
INFO: 74% (149.3 GiB of 200.0 GiB) in 1m 28s, read: 4.1 GiB/s, write: 221.4 MiB/s
INFO: 76% (152.9 GiB of 200.0 GiB) in 1m 31s, read: 1.2 GiB/s, write: 500.7 MiB/s
INFO: 85% (170.6 GiB of 200.0 GiB) in 1m 34s, read: 5.9 GiB/s, write: 45.9 MiB/s
INFO: 94% (189.5 GiB of 200.0 GiB) in 1m 37s, read: 6.3 GiB/s, write: 12.0 KiB/s
INFO: 100% (200.0 GiB of 200.0 GiB) in 1m 39s, read: 5.2 GiB/s, write: 131.0 MiB/s
INFO: backup is sparse: 155.44 GiB (77%) total zero data
INFO: transferred 200.00 GiB in 99 seconds (2.0 GiB/s)
INFO: stopping kvm after backup task
INFO: archive file size: 12.56GB
INFO: adding notes to backup
INFO: prune older backups with retention: keep-last=2
INFO: removing backup 'Backup:backup/vzdump-qemu-102-2025_12_07-01_00_29.vma.zst'
INFO: pruned 1 backup(s) not covered by keep-retention policy
INFO: Finished Backup of VM 102 (00:01:42)
INFO: Backup finished at 2025-12-08 10:42:59
INFO: Backup job finished with errors
INFO: notified via target `mail-to-root`
TASK ERROR: job errors@gfngfn256 has a very good point. Since
So the current issue is not that it uses temporary space but that it tries to Back up to the OS drive which only has 96G.
/mnt/usb-backup isn't its own mount point, the data will be stored inside a directory on the root / path. I missed this.So the current issue is not that it uses temporary space but that it tries to Back up to the OS drive which only has 96G.
Last edited:
Yes it is a USB attached drive where I want the backups to be stored. I mounted it at /mnt/usb-backup. I had temporarily mounted it at /media/simon/backup and forgot to unmount it.
Code:
root@minipc:/# df -H
Filesystem Size Used Avail Use% Mounted on
udev 63G 0 63G 0% /dev
tmpfs 13G 3.9M 13G 1% /run
/dev/mapper/pve-root 101G 60G 36G 63% /
tmpfs 64G 66M 64G 1% /dev/shm
efivarfs 132k 48k 79k 38% /sys/firmware/efi/efivars
tmpfs 1.1M 0 1.1M 0% /run/credentials/systemd-journald.service
tmpfs 5.3M 13k 5.3M 1% /run/lock
tmpfs 64G 8.2k 64G 1% /tmp
/dev/nvme1n1p2 1.1G 764M 308M 72% /boot/efi
/dev/fuse 135M 21k 135M 1% /etc/pve
tmpfs 1.1M 0 1.1M 0% /run/credentials/getty@tty1.service
tmpfs 13G 87k 13G 1% /run/user/1000
tmpfs 13G 74k 13G 1% /run/user/0
Unless you have ~55GB of iso files - this pretty much confirms your above backup is being stored locally on
/mnt/usb-backup NOT on the (un)mounted usb-attached drive.A simple check: remove the usb-drive & check
ls /mnt/usb-backup. If it contains anything - case closed.So there is data in /mnt/usb-backup when the USB is unplugged.
Code:
root@minipc:/# blkid
/dev/mapper/pve-root: UUID="b5b1c498-3650-479a-affc-b164cb880a17" BLOCK_SIZE="4096" TYPE="ext4"
/dev/nvme0n1: UUID="l6tuDR-h8VW-sNo1-o9De-DGfj-AJZQ-sgDuLM" TYPE="LVM2_member"
/dev/mapper/pve-swap: UUID="09d31a45-ed19-434c-8565-e60a94a6851c" TYPE="swap"
/dev/nvme1n1p2: UUID="98AC-798B" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="d4b48c80-7603-4c52-b169-6afc39f8a2fa"
/dev/nvme1n1p3: UUID="w8nYVX-Hqsq-LOaH-6bsE-cTPZ-Fz10-k4w9gl" TYPE="LVM2_member" PARTUUID="15b2b462-8389-4d91-828f-88e69c332ae9"
/dev/mapper/Main2TB-vm--101--disk--0: PTUUID="f7e9373d-9500-430d-89bb-16f440601696" PTTYPE="gpt"
/dev/mapper/Main2TB-vm--102--disk--0: PTUUID="35caaeca-fee9-48ac-b5dd-f91c1fa8d587" PTTYPE="gpt"
/dev/nvme1n1p1: PARTUUID="f97cdc9b-8123-4b6b-a2f6-2c48e27c0846"This is with the USB plugged in:
Code:
root@minipc:/# blkid
/dev/mapper/pve-root: UUID="b5b1c498-3650-479a-affc-b164cb880a17" BLOCK_SIZE="4096" TYPE="ext4"
/dev/nvme0n1: UUID="l6tuDR-h8VW-sNo1-o9De-DGfj-AJZQ-sgDuLM" TYPE="LVM2_member"
/dev/mapper/pve-swap: UUID="09d31a45-ed19-434c-8565-e60a94a6851c" TYPE="swap"
/dev/nvme1n1p2: UUID="98AC-798B" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="d4b48c80-7603-4c52-b169-6afc39f8a2fa"
/dev/nvme1n1p3: UUID="w8nYVX-Hqsq-LOaH-6bsE-cTPZ-Fz10-k4w9gl" TYPE="LVM2_member" PARTUUID="15b2b462-8389-4d91-828f-88e69c332ae9"
/dev/mapper/Main2TB-vm--101--disk--0: PTUUID="f7e9373d-9500-430d-89bb-16f440601696" PTTYPE="gpt"
/dev/mapper/Main2TB-vm--102--disk--0: PTUUID="35caaeca-fee9-48ac-b5dd-f91c1fa8d587" PTTYPE="gpt"
/dev/nvme1n1p1: PARTUUID="f97cdc9b-8123-4b6b-a2f6-2c48e27c0846"
/dev/sda1: LABEL="backup" UUID="7751d33a-13dc-45f2-83b3-49016c708672" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="2b303f31-d752-4f86-8730-b8e104914f18"