lzop: Input/output error: <stdout>

S

soniaslimani8

New Member
Oct 21, 2020
9
0
1
33
Hi,
I have this error when I try to Backup jenkinsdev:

INFO: status: 11% (141742571520/1288490188800), sparse 0% (6855868416), duration 10929, read/write 13/12 MB/s
INFO: status: 12% (154628259840/1288490188800), sparse 0% (7137296384), duration 12017, read/write 11/11 MB/s
lzop: Input/output error: <stdout>
INFO: status: 12% (164761960448/1288490188800), sparse 0% (7867379712), duration 12746, read/write 13/12 MB/s
Warning: unable to close filehandle GEN43015 properly: Input/output error at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 453.
ERROR: vma_queue_write: write error - Broken pipe
INFO: aborting backup job
ERROR: Backup of VM 172 failed - vma_queue_write: write error - Broken pipe
INFO: Backup job finished with errors
TASK ERROR: job errors

Anyone have an idea how to fix this please?
 
This is happening to me too on 6.2-12
Target is a local nfs, only happens on one of my QM's and it locks up the VM instance that I need to hard stop and start after every node backup.

INFO: creating vzdump archive '/mnt/pve/Backup-1n1/dump/vzdump-qemu-110-2020_10_22-19_30_02.vma.lzo'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task 'cf775604-48f9-4c3a-a6d5-d32a887fa96a'
INFO: resuming VM again
INFO: 0% (749.9 MiB of 1000.0 GiB) in 3s, read: 250.0 MiB/s, write: 46.1 MiB/s
INFO: 1% (10.0 GiB of 1000.0 GiB) in 3m 56s, read: 40.8 MiB/s, write: 40.0 MiB/s
lzop: Input/output error: <stdout>
Warning: unable to close filehandle GEN69 properly: Input/output error at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 752.
ERROR: VM 110 qmp command 'query-backup' failed - got timeout
INFO: aborting backup job
ERROR: VM 110 qmp command 'backup-cancel' failed - unable to connect to VM 110 qmp socket - timeout after 5980 retries
ERROR: Backup of VM 110 failed - VM 110 qmp command 'query-backup' failed - got timeout
INFO: Failed at 2020-10-22 19:54:58
INFO: Backup job finished with errors


When attempting to access the console after this it complains about qmp timeouts. I'm confused by why this happens if the VM resumes as soon as fs-thaw is issued.....

qemu-agent is installed and verified.
 
I just switched it to suspend mode backup, will report if there's a change
 
Same result using suspend backup, and ZSTD.

INFO: suspending guest
INFO: creating vzdump archive '/mnt/pve/Backup-1n1/dump/vzdump-qemu-110-2020_10_24-00_00_02.vma.zst'
INFO: skipping guest-agent 'fs-freeze', agent configured but not running?
INFO: started backup task '7b5b2435-087d-470a-a81f-f6af9a3376c5'
INFO: resuming VM again after 4 seconds
INFO: 0% (478.5 MiB of 1000.0 GiB) in 3s, read: 159.5 MiB/s, write: 9.3 MiB/s
INFO: 1% (10.0 GiB of 1000.0 GiB) in 2m 51s, read: 58.2 MiB/s, write: 56.2 MiB/s
zstd: error 25 : Write error : Input/output error (cannot write compressed block)
Warning: unable to close filehandle GEN75 properly: Input/output error at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 752.
ERROR: VM 110 qmp command 'query-backup' failed - got timeout
INFO: aborting backup job
ERROR: VM 110 qmp command 'backup-cancel' failed - unable to connect to VM 110 qmp socket - timeout after 5981 retries
INFO: resume vm
INFO: VM 110 qmp command 'query-status' failed - unable to connect to VM 110 qmp socket - timeout after 31 retries
command 'qm resume 110 --skiplock' failed: exit code 255
ERROR: Backup of VM 110 failed - VM 110 qmp command 'query-backup' failed - got timeout
INFO: Failed at 2020-10-24 00:25:06
INFO: Backup job finished with errors

Trying STOP mode backup tonight (Though I don't want to.)
 
jdye said:
Same result using suspend backup, and ZSTD.

INFO: suspending guest
INFO: creating vzdump archive '/mnt/pve/Backup-1n1/dump/vzdump-qemu-110-2020_10_24-00_00_02.vma.zst'
INFO: skipping guest-agent 'fs-freeze', agent configured but not running?
INFO: started backup task '7b5b2435-087d-470a-a81f-f6af9a3376c5'
INFO: resuming VM again after 4 seconds
INFO: 0% (478.5 MiB of 1000.0 GiB) in 3s, read: 159.5 MiB/s, write: 9.3 MiB/s
INFO: 1% (10.0 GiB of 1000.0 GiB) in 2m 51s, read: 58.2 MiB/s, write: 56.2 MiB/s
zstd: error 25 : Write error : Input/output error (cannot write compressed block)
Warning: unable to close filehandle GEN75 properly: Input/output error at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 752.
ERROR: VM 110 qmp command 'query-backup' failed - got timeout
INFO: aborting backup job
ERROR: VM 110 qmp command 'backup-cancel' failed - unable to connect to VM 110 qmp socket - timeout after 5981 retries
INFO: resume vm
INFO: VM 110 qmp command 'query-status' failed - unable to connect to VM 110 qmp socket - timeout after 31 retries
command 'qm resume 110 --skiplock' failed: exit code 255
ERROR: Backup of VM 110 failed - VM 110 qmp command 'query-backup' failed - got timeout
INFO: Failed at 2020-10-24 00:25:06
INFO: Backup job finished with errors

Trying STOP mode backup tonight (Though I don't want to.)
Click to expand...
Hi, any updates about the use of STOP mode, did the error disappear now?
 
Well, problem with STOP mode is HA....

INFO: starting new backup job: vzdump 110 --mode stop --mailnotification always --storage Backup-1n1 --quiet 1 --compress zstd
ERROR: Backup of VM 110 failed - Cannot execute a backup with stop mode on a HA managed and enabled Service. Use snapshot mode or disable the Service.
INFO: Failed at 2020-10-26 00:00:02
INFO: Backup job finished with errors
 
jdye said:
Well, problem with STOP mode is HA....

INFO: starting new backup job: vzdump 110 --mode stop --mailnotification always --storage Backup-1n1 --quiet 1 --compress zstd
ERROR: Backup of VM 110 failed - Cannot execute a backup with stop mode on a HA managed and enabled Service. Use snapshot mode or disable the Service.
INFO: Failed at 2020-10-26 00:00:02
INFO: Backup job finished with errors
Click to expand...
I think the problem that the space is not enough to store temporary files during Backup, I did df -h during the backup and I found that the space of /tmp progressively achieve 100%, than the backup failed, but I don't know where I should store cache to have enough space during backup.
 
I'm still having the same issues, I had to disable HA on the VM I was having this error on, and use STOP mode backup.

I'm not sure what the issue is, I watched my df during a backup and didn't see /tmp run out of space. But could have been a fluke.
 
Stop mode didn't with for me either, wondering if this is because my qcow2 is in raw mode, what's yours?
 
You must log in or register to reply here.
Top Bottom