Unable to Backup VM: "write error - Broken pipe"

[naupe]

So I've been successful in backing up my small VMs (3 of them around 5-15 GB in size) and they backed up just fine. I've scp'd the GZIPs to a Backup External Drive (so they aren't taking up space on the Proxmox Server).

I've also got a VM that is about 85GB in disk space. Unfortunately, I've been unable to back it up properly. Tried backing it up 2 times, both stopped backing up at 25%:

2020-04-15 08:15:22 INFO: Starting Backup of VM 101 (qemu)
2020-04-15 08:15:22 INFO: status = running
2020-04-15 08:15:23 INFO: update VM 101: -lock backup
2020-04-15 08:15:23 INFO: VM Name: GitLab
2020-04-15 08:15:23 INFO: include disk 'scsi0' 'local-lvm:vm-101-disk-0' 500G
2020-04-15 08:15:23 INFO: backup mode: snapshot
2020-04-15 08:15:23 INFO: ionice priority: 7
2020-04-15 08:15:23 INFO: snapshots found (not included into backup)
2020-04-15 08:15:23 INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-101-2020_04_15-08_15_22.vma.gz'
2020-04-15 08:15:23 INFO: started backup task '2b2eda2a-5e56-4350-8799-74cd2104a5c0'
2020-04-15 08:15:26 INFO: status: 0% (155844608/536870912000), sparse 0% (130048000), duration 3, read/write 51/8 MB/s
2020-04-15 08:24:00 INFO: status: 1% (5374738432/536870912000), sparse 0% (537120768), duration 517, read/write 10/9 MB/s
2020-04-15 08:33:01 INFO: status: 2% (10741874688/536870912000), sparse 0% (731623424), duration 1058, read/write 9/9 MB/s
2020-04-15 08:42:09 INFO: status: 3% (16111501312/536870912000), sparse 0% (802394112), duration 1606, read/write 9/9 MB/s
2020-04-15 08:51:19 INFO: status: 4% (21476147200/536870912000), sparse 0% (906133504), duration 2156, read/write 9/9 MB/s
2020-04-15 09:00:27 INFO: status: 5% (26847084544/536870912000), sparse 0% (982360064), duration 2704, read/write 9/9 MB/s
2020-04-15 09:09:40 INFO: status: 6% (32220184576/536870912000), sparse 0% (1161129984), duration 3257, read/write 9/9 MB/s
2020-04-15 09:19:29 INFO: status: 7% (37588959232/536870912000), sparse 0% (1293033472), duration 3846, read/write 9/8 MB/s
2020-04-15 09:28:23 INFO: status: 8% (42959896576/536870912000), sparse 0% (1662128128), duration 4380, read/write 10/9 MB/s
2020-04-15 09:37:31 INFO: status: 9% (48319430656/536870912000), sparse 0% (1921703936), duration 4928, read/write 9/9 MB/s
2020-04-15 09:46:09 INFO: status: 10% (53690368000/536870912000), sparse 0% (2401689600), duration 5446, read/write 10/9 MB/s
2020-04-15 09:54:49 INFO: status: 11% (59061305344/536870912000), sparse 0% (2864365568), duration 5966, read/write 10/9 MB/s
2020-04-15 10:03:26 INFO: status: 12% (64428441600/536870912000), sparse 0% (3386912768), duration 6483, read/write 10/9 MB/s
2020-04-15 10:12:09 INFO: status: 13% (69793939456/536870912000), sparse 0% (3833384960), duration 7006, read/write 10/9 MB/s
2020-04-15 10:21:10 INFO: status: 14% (75166515200/536870912000), sparse 0% (4079501312), duration 7547, read/write 9/9 MB/s
2020-04-15 10:30:26 INFO: status: 15% (80533651456/536870912000), sparse 0% (4174639104), duration 8103, read/write 9/9 MB/s
2020-04-15 10:39:15 INFO: status: 16% (85900787712/536870912000), sparse 0% (4501721088), duration 8632, read/write 10/9 MB/s
2020-04-15 10:48:06 INFO: status: 17% (91271725056/536870912000), sparse 0% (4767862784), duration 9163, read/write 10/9 MB/s
2020-04-15 10:56:45 INFO: status: 18% (96637550592/536870912000), sparse 0% (5194858496), duration 9682, read/write 10/9 MB/s
2020-04-15 11:05:26 INFO: status: 19% (102013599744/536870912000), sparse 1% (5527158784), duration 10203, read/write 10/9 MB/s
2020-04-15 11:14:17 INFO: status: 20% (107380736000/536870912000), sparse 1% (5940285440), duration 10734, read/write 10/9 MB/s
2020-04-15 11:23:22 INFO: status: 21% (112747216896/536870912000), sparse 1% (6204514304), duration 11279, read/write 9/9 MB/s
2020-04-15 11:32:14 INFO: status: 22% (118115008512/536870912000), sparse 1% (6599266304), duration 11811, read/write 10/9 MB/s
2020-04-15 11:41:12 INFO: status: 23% (123485945856/536870912000), sparse 1% (6884835328), duration 12349, read/write 9/9 MB/s
2020-04-15 11:49:59 INFO: status: 24% (128853082112/536870912000), sparse 1% (7282401280), duration 12876, read/write 10/9 MB/s
2020-04-15 11:59:19 INFO: status: 25% (134224019456/536870912000), sparse 1% (7554420736), duration 13436, read/write 9/9 MB/s
2020-04-15 12:02:29 INFO: status: 25% (136151171072/536870912000), sparse 1% (7686811648), duration 13626, read/write 10/9 MB/s
2020-04-15 12:02:29 ERROR: vma_queue_write: write error - Broken pipe
2020-04-15 12:02020-04-15 12:02:36 ERROR: Backup of VM 101 failed - vma_queue_write: write error - Broken pipe

I thought the issue might be disk space ... but I've got more then 85 GB reserved to Proxmox. I would also think that if disk space was the issue, the log would say such.

Any other ideas? The default Backup Directory looks to be /var/lib/vz/dump

 

[tim]

By default the /var/lib/vz/dump directory is on your root partition which isn't that big with default installations, you should check that and your backup location.

 

[Jarvar]

Just to chime in. I recently kept getting this similar error. It took a reboot of my system in order to clear the tmp file that was created since it resulted into an insufficient storage error when trying to utilize the GUI. Anyways, is there a method to get a VZdump elsewhere? I am running dual drive 240GB on ZFS and dual 1TB storage ZFS drives to store the VM. The local disk /var/lib.vz/dump has run out of space with only roughly ~200GB free to begin with. I am backing up also to Proxmox Backup Server remotely, but would be nice to get a full vzdump which I can rsync to another location.... Any help would be greatly appreciated. Thanks.