Backup error - Warning: unable to close filehandle GEN163 properly: Input/output error at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 777.

[komp]

Hello
Got this error sometimes while run backup with different VMs to NFS storage:

INFO: starting new backup job: vzdump 126 --compress zstd --notes-template '{{guestname}}' --prune-backups 'keep-last=4' --storage Backup-1 --mode snapshot --quiet 1 --mailto [hidden] --mailnotification failure
INFO: Starting Backup of VM 126 (qemu)
INFO: Backup started at 2022-09-24 02:50:02
INFO: status = running
INFO: VM Name: Pinger
INFO: include disk 'scsi0' 'CEPH_Storage:vm-126-disk-0' 16G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: skip unused drive 'SSD-Storage-1:126/vm-126-disk-0.qcow2' (not included into backup)
INFO: creating vzdump archive '/mnt/pve/Backup-1/dump/vzdump-qemu-126-2022_09_24-02_50_02.vma.zst'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '500744be-dfbd-4608-afda-ae0c81c7d917'
INFO: resuming VM again
INFO:   7% (1.2 GiB of 16.0 GiB) in 3s, read: 401.2 MiB/s, write: 345.9 MiB/s
INFO:   8% (1.4 GiB of 16.0 GiB) in 12s, read: 26.6 MiB/s, write: 26.5 MiB/s
INFO:  12% (1.9 GiB of 16.0 GiB) in 15s, read: 183.7 MiB/s, write: 183.5 MiB/s
INFO:  17% (2.7 GiB of 16.0 GiB) in 18s, read: 270.6 MiB/s, write: 266.7 MiB/s
INFO:  22% (3.5 GiB of 16.0 GiB) in 21s, read: 273.1 MiB/s, write: 253.0 MiB/s
INFO:  26% (4.3 GiB of 16.0 GiB) in 24s, read: 264.6 MiB/s, write: 260.9 MiB/s
INFO:  33% (5.3 GiB of 16.0 GiB) in 27s, read: 339.5 MiB/s, write: 335.9 MiB/s
INFO:  42% (6.8 GiB of 16.0 GiB) in 30s, read: 525.6 MiB/s, write: 290.7 MiB/s
INFO:  52% (8.3 GiB of 16.0 GiB) in 33s, read: 503.9 MiB/s, write: 252.9 MiB/s
INFO:  57% (9.2 GiB of 16.0 GiB) in 36s, read: 296.0 MiB/s, write: 294.9 MiB/s
INFO:  71% (11.4 GiB of 16.0 GiB) in 39s, read: 745.7 MiB/s, write: 321.5 MiB/s
INFO: 100% (16.0 GiB of 16.0 GiB) in 41s, read: 2.3 GiB/s, write: 116.8 MiB/s
INFO: backup is sparse: 7.32 GiB (45%) total zero data
INFO: transferred 16.00 GiB in 41 seconds (399.6 MiB/s)
Warning: unable to close filehandle GEN163 properly: Input/output error at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 777.
zstd: /*stdout*\: Input/output error
ERROR: Backup of VM 126 failed - zstd --rsyncable --threads=1 failed - wrong exit status 1
INFO: Failed at 2022-09-24 02:51:26
INFO: Backup job finished with errors
TASK ERROR: job errors

Kernel Version -  Linux 5.15.53-1-pve #1 SMP PVE 5.15.53-1 (Fri, 26 Aug 2022 16:53:52 +0200)
PVE Manager Version  - pve-manager/7.2-11/b76d3178

Package versions:

proxmox-ve: 7.2-1 (running kernel: 5.15.53-1-pve)
pve-manager: 7.2-11 (running version: 7.2-11/b76d3178)
pve-kernel-helper: 7.2-12
pve-kernel-5.15: 7.2-10
pve-kernel-5.15.53-1-pve: 5.15.53-1
pve-kernel-5.15.39-4-pve: 5.15.39-4
pve-kernel-5.15.39-3-pve: 5.15.39-3
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph: 17.2.1-pve1
ceph-fuse: 17.2.1-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-8
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
openvswitch-switch: 2.15.0+ds1-2+deb11u1
proxmox-backup-client: 2.2.6-1
proxmox-backup-file-restore: 2.2.6-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-2
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-3
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.5-pve1

 

[komp]

Any ideas why this error can appear?

 

[komp]

Is there any chance of getting help? The error continues to happen from time to time.

 

[Neobin]

Is there any chance of getting help?

An option would be, to get a "basic" or higher subscription [1] (if not already present) and open a support ticket.

[1] https://proxmox.com/en/proxmox-ve/pricing

 

[greenie]

An option would be, to get a "basic" or higher subscription [1] (if not already present) and open a support ticket.

[1] https://proxmox.com/en/proxmox-ve/pricing

this really isnt very helpful. The only solution cannot be pay for someone to fix it. There are many issues that are raised on this forum that get replies for free.

Is there any chance of getting help? The error continues to happen from time to time.

if this post isnt gaining traction maybe head to the unofficial discord, many active users that will be willing to help. im currently facing the same issue and looking for a solution, if i find one or steps to get closer to a fix ill edit this comment / reply again

 

[Neobin]

this really isnt very helpful. The only solution cannot be pay for someone to fix it. There are many issues that are raised on this forum that get replies for free.

While this forum is absolutely awesome in regards of helpfulness, not only from other users, but also from the Proxmox staff/developers themselves (without having to pay anything for this first-hand support!), it also does not guarantee that one gets a solution to a problem or even an answer at all.

I (and I guess you too?) do not know in which environment the OP encountered this problem (btw: over a year ago).
So, if this is e.g. in a production/business environment and he encounters the problem for, at least, almost a month (the time between starting this thread and his last post in it) and he unfortunately did not get an answer here nor found a solution elsewhere in this time, giving him the information where he can get guaranteed first-hand support is, imho, not wrong.
I can not know, if someone is already aware of this option, so giving him this information does not hurt or does it?
It is only meant informative, in case someone is not aware; nothing more!

PS.:
Other solutions, not only speaking of hypervisors but in general, do not even provide an official support forum or if they do, there is no support from the staff/developers themselves at all.
So, if one got a problem, that one can not solve himself by "googling" and/or other (non-staff/-developer) users in e.g. a forum, one has to pay ever to get first-hand support from e.g. the support staff and/or developers...

PPS.:
However, this:

The only solution cannot be pay for someone to fix it.

statement already says a lot...

 

[komp]

If anyone is interested, in the end I just switched from NFS storage to Proxmox Backup Server.

 

[kiotech]

I encountered a similar error using SMB & proxmox 8.3.1.
The problem was solved by using gzip compression mode instead of ZSTD.

INFO: transferred 32.00 GiB in 127 seconds (258.0 MiB/s)
zstd: /*stdout*\: Software caused connection abort 
Warning: unable to close filehandle GEN2176 properly: Software caused connection abort at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 976.
ERROR: Backup of VM 106 failed - zstd --threads=1 failed - wrong exit status 1
INFO: Failed at 2024-12-14 21:22:53
INFO: Backup job finished with errors
TASK ERROR: job errors