Vzdump failed du to too little space left

A

adrian_vg

Active Member
Mar 8, 2020
74
26
28
Sweden
Hello all!

I seem to be running into the same error as the user in this thread:

https://forum.proxmox.com/threads/backup-failed-vma_queue_write-write-error-broken-pipe.26232/

User jct never wrote anything about how to move the backup location.
In my case it'd seem the backups are saved in "local" storage:

Code: 
INFO: starting new backup job: vzdump 104 113 114 --quiet 1 --mode stop --mailnotification always --node dragonborn --compress zstd --storage local --mailto some.address@example.com
...
INFO: creating vzdump archive '/var/lib/vz/dump/vzdump-qemu-104-2021_03_12-00_00_04.vma.zst'
...
INFO:  44% (28.2 GiB of 64.0 GiB) in 19m 16s, read: 31.6 MiB/s, write: 29.8 MiB/s
zstd: error 25 : Write error : No space left on device (cannot write compressed block)
INFO:  44% (28.6 GiB of 64.0 GiB) in 19m 34s, read: 24.1 MiB/s, write: 24.1 MiB/s
ERROR: vma_queue_write: write error - Broken pipe
INFO: aborting backup job
ERROR: Backup of VM 104 failed - vma_queue_write: write error - Broken pipe
INFO: Failed at 2021-03-12 00:20:37

Can the backup location be changed to a storage with more space available using "--storage local-lvm" or some such?
Am not sure how to best proceed with this problem.
Any hints or comments please?

Thanks!

Code: 
root@dragonborn:~# lsblk
NAME                         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda                            8:0    0  9,1T  0 disk
├─sda1                         8:1    0 1007K  0 part
├─sda2                         8:2    0  512M  0 part
└─sda3                         8:3    0  9,1T  0 part
  ├─pve-swap                 253:0    0    2G  0 lvm  [SWAP]
  ├─pve-root                 253:1    0   96G  0 lvm  /
  ├─pve-data_tmeta           253:2    0 15,8G  0 lvm 
  │ └─pve-data-tpool         253:4    0    9T  0 lvm 
  │   ├─pve-data             253:5    0    9T  0 lvm 
  │   ├─pve-vm--100--disk--0 253:6    0   32G  0 lvm 
  │   ├─pve-vm--100--disk--1 253:7    0  3,1T  0 lvm 
  │   ├─pve-vm--112--disk--0 253:8    0   32G  0 lvm 
  │   ├─pve-vm--113--disk--0 253:9    0   32G  0 lvm 
  │   ├─pve-vm--101--disk--0 253:11   0   32G  0 lvm 
  │   ├─pve-vm--111--disk--0 253:12   0   32G  0 lvm 
  │   ├─pve-vm--111--disk--1 253:13   0   32G  0 lvm 
  │   ├─pve-vm--102--disk--0 253:15   0   32G  0 lvm 
  │   ├─pve-vm--104--disk--0 253:16   0   64G  0 lvm 
  │   ├─pve-vm--105--disk--0 253:17   0   32G  0 lvm 
  │   ├─pve-vm--109--disk--0 253:18   0 1000G  0 lvm 
  │   ├─pve-vm--107--disk--1 253:20   0  120G  0 lvm 
  │   └─pve-vm--116--disk--0 253:21   0   32G  0 lvm 
  └─pve-data_tdata           253:3    0    9T  0 lvm 
    └─pve-data-tpool         253:4    0    9T  0 lvm 
      ├─pve-data             253:5    0    9T  0 lvm 
      ├─pve-vm--100--disk--0 253:6    0   32G  0 lvm 
      ├─pve-vm--100--disk--1 253:7    0  3,1T  0 lvm 
      ├─pve-vm--112--disk--0 253:8    0   32G  0 lvm 
      ├─pve-vm--113--disk--0 253:9    0   32G  0 lvm 
      ├─pve-vm--101--disk--0 253:11   0   32G  0 lvm 
      ├─pve-vm--111--disk--0 253:12   0   32G  0 lvm 
      ├─pve-vm--111--disk--1 253:13   0   32G  0 lvm 
      ├─pve-vm--102--disk--0 253:15   0   32G  0 lvm 
      ├─pve-vm--104--disk--0 253:16   0   64G  0 lvm 
      ├─pve-vm--105--disk--0 253:17   0   32G  0 lvm 
      ├─pve-vm--109--disk--0 253:18   0 1000G  0 lvm 
      ├─pve-vm--107--disk--1 253:20   0  120G  0 lvm 
      └─pve-vm--116--disk--0 253:21   0   32G  0 lvm 
sr0                           11:0    1 1024M  0 rom



Code: 
root@dragonborn:~# vgs
  VG  #PV #LV #SN Attr   VSize VFree 
  pve   1  34   0 wz--n- 9,09t <16,38g



Code: 
root@dragonborn:~# lvs
  LV                               VG  Attr       LSize    Pool Origin        Data%  Meta%  Move Log Cpy%Sync Convert
  data                             pve twi-aotz--    8,95t                    40,09  9,83                           
  root                             pve -wi-ao----   96,00g                                                           
  snap_vm-100-disk-0_nfs05         pve Vri---tz-k   32,00g data vm-100-disk-0                                       
  snap_vm-100-disk-1_nfs05         pve Vri---tz-k    3,12t data vm-100-disk-1                                       
  snap_vm-102-disk-0_ssh_portal001 pve Vri---tz-k   32,00g data vm-102-disk-0                                       
  snap_vm-102-disk-0_ssh_portal003 pve Vri---tz-k   32,00g data vm-102-disk-0                                       
  snap_vm-104-disk-0_joomla15      pve Vri---tz-k   32,00g data vm-104-disk-0                                       
  snap_vm-104-disk-0_joomla19      pve Vri---tz-k   64,00g data vm-104-disk-0                                       
  snap_vm-104-disk-0_joomla20      pve Vri---tz-k   64,00g data vm-104-disk-0                                       
  snap_vm-109-disk-0_nc009         pve Vri---tz-k 1000,00g data vm-109-disk-0                                       
  snap_vm-109-disk-0_nc010         pve Vri---tz-k 1000,00g data vm-109-disk-0                                       
  snap_vm-111-disk-0_stk02         pve Vri---tz-k   32,00g data vm-111-disk-0                                       
  snap_vm-111-disk-1_stk02         pve Vri---tz-k   32,00g data vm-111-disk-1                                       
  snap_vm-112-disk-0_docker001     pve Vri---tz-k   32,00g data vm-112-disk-0                                       
  snap_vm-112-disk-0_docker002     pve Vri---tz-k   32,00g data vm-112-disk-0                                       
  snap_vm-113-disk-0_jenkins01     pve Vri---tz-k   32,00g data vm-113-disk-0                                       
  snap_vm-113-disk-0_jenkins07     pve Vri---tz-k   32,00g data vm-113-disk-0                                       
  snap_vm-113-disk-0_jenkins08     pve Vri---tz-k   32,00g data vm-113-disk-0                                       
  snap_vm-116-disk-0_dns2_002      pve Vri---tz-k   32,00g data vm-116-disk-0                                       
  snap_vm-116-disk-0_dns2_01       pve Vri---tz-k   32,00g data vm-116-disk-0                                       
  swap                             pve -wi-ao----    2,00g                                                           
  vm-100-disk-0                    pve Vwi-aotz--   32,00g data               96,60                                 
  vm-100-disk-1                    pve Vwi-aotz--    3,12t data               77,59                                 
  vm-101-disk-0                    pve Vwi-a-tz--   32,00g data               52,26                                 
  vm-102-disk-0                    pve Vwi-aotz--   32,00g data               31,30                                 
  vm-104-disk-0                    pve Vwi-aotz--   64,00g data               96,48                                 
  vm-105-disk-0                    pve Vwi-a-tz--   32,00g data               19,57                                 
  vm-107-disk-1                    pve Vwi-a-tz--  120,00g data               17,17                                 
  vm-109-disk-0                    pve Vwi-aotz-- 1000,00g data               68,72                                 
  vm-111-disk-0                    pve Vwi-a-tz--   32,00g data               47,41                                 
  vm-111-disk-1                    pve Vwi-a-tz--   32,00g data               0,00                                   
  vm-112-disk-0                    pve Vwi-aotz--   32,00g data               54,51                                 
  vm-113-disk-0                    pve Vwi-aotz--   32,00g data               77,60                                 
  vm-116-disk-0                    pve Vwi-aotz--   32,00g data               28,54
 
You simply need to create a new backup storage target and choose it while making backups.

"Datacenter => Storage => Add" (You need to choose the type where to do backups directory, nfs, ceph for example)
But it looks like your storage is full anyway, so you need a network attached storage to make backups on (CIFS,NFS)

When you create the new Storage, you need to select "VZDump backup file" in the "Content" Section and select the name of the new storage
in the backup job. (When u click on a VM, then Backup it shows the Storage in the top right corner.
 
  • Like
Reactions: Universal4 and adrian_vg
AKA said:
You simply need to create a new backup storage target and choose it while making backups.

"Datacenter => Storage => Add" (You need to choose the type where to do backups directory, nfs, ceph for example)
But it looks like your storage is full anyway, so you need a network attached storage to make backups on (CIFS,NFS)

When you create the new Storage, you need to select "VZDump backup file" in the "Content" Section and select the name of the new storage
in the backup job. (When u click on a VM, then Backup it shows the Storage in the top right corner.
Click to expand...
Gotcha', thanks!
Set it up just now and am testing it.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back