Backup issue - broken but finished successfully

[steffenk]

hello,

i know that i ran out off disk-space.
But this task (normally the backup is 90 GB) end up successfully (backup is not recoverable) and i get no email (only error)
-----
Warning: unable to close filehandle GEN56 properly: No space left on device at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 510.
INFO: archive file size: 71.71GB
INFO: delete old backup '/mnt/backup/dump/vzdump-qemu-600-2019_10_29-02_00_02.vma.lzo'
INFO: Finished Backup of VM 600 (00:57:33)
INFO: Backup finished at 2019-11-05 02:57:35
INFO: Backup job finished successfully
----
Software is up2date:

Virtual Environment 6.0-9
Kernelversion: Linux 5.0.21-3-pve #1 SMP PVE 5.0.21-7
PVE Manager Version: pve-manager/6.0-9/508dcee0

-----

ist this a bug or a config mistake?

kind regards

Steffen Klein

 

[tim]

Clearly both, the backup job shouldn't report a successful backup if there's an error on the other hand things get shady when there's no space left on the target. You can open a bug in our bug tracker (https://bugzilla.proxmox.com/) if you like, but in my opinion this will not get prioritized, because this is very easy to mitigate just make sure there's enough space left before backup .

 

[steffenk]

hi tim,

thanks for the answer.you are right, monitoring backup space is the better option i was just confused about the "successfully" status.

best regards,

steffen klein

 

[Asano]

I just saw the exact same error and successful finish. However there were over 2TB left free on the target storage (a Synology CIFS share) and the backup had below 40GB.

I could imagine that the success message was actually valid. When I repeated the backup directly afterwards it went through without the error. And then I saw that the first backup (with the error message) triggered the Synology 20% storage warning. I really don't know much about (network) file systems but could it be possible that there was some kind 'full' warning without actually preventing further write operations which triggered this error?

In either case I also see this as very low piro, so just some information which may be interesting...