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.