#1 2018-12-03 09:16:26

tpau86
Member
Registered: 2018-12-03
Posts: 2

rsync: write failed

Hello,

I have a job that has been running fine for a few months which back-ups 4 guests machines all have worked in the past. However, one of the guests and only one now shows this:

[ Sat Dec 1 08:00:18 UTC 2018 ] ERROR CLXSITO1 details: [Vulcan] error: rsync error details: rsync: write failed on /vmfs/volumes/DCNX/ESXi/20181201080018/Vulcan/vulcan-flat.vmdk: Input/output error (5) rsync error: error in file IO (code 11) at receiver.c(389) [receiver=3.1.0] [sender] io timeout after 60 seconds -- exiting

It seems to backup the vmdk, then halt, then timeout and delete the vmdk and report the above message, all other VM's on the same host going to the same backup array all work so I'm confused on why only this one is failing.

Any ideas?

Last edited by tpau86 (2018-12-03 15:40:55)

Offline

#2 2018-12-04 17:40:55

admin
Administrator
Registered: 2017-04-21
Posts: 563

Re: rsync: write failed

This kind of message:

Input/output error (5) rsync error: error in file IO (code 11) at receiver.c(389)

Is thrown when some sort of lower level problem occurs: hardware or communications error. If I were you I would quickly run some S.M.A.R.T. diagnostic on your disks and check everything regarding the reliability of the network in between. The fact that it's always the same VM that fails may have to do with some particular portion of the disk being damaged. There could also be some recurring network instability happening at about the same time every day, try to delve a bit by changing the VM backup order, although it seems a disk IO error, most probably your disk is starting to fail.

Offline

#3 2018-12-04 19:22:21

tpau86
Member
Registered: 2018-12-03
Posts: 2

Re: rsync: write failed

Thanks for the response, it is really appreciated. I've tried the job at random times and it still fails, so I agree with you I doubt it's network.

I've closed the VM and used scp and it works, but a manually rsync still fails with the VM down. Being many other jobs are writing to the backup NAS and hence a different inodes and locations are being used, would you agree it might be a failure/failing of the source media?

Last edited by tpau86 (2018-12-04 19:23:56)

Offline

#4 2018-12-04 20:34:51

admin
Administrator
Registered: 2017-04-21
Posts: 563

Re: rsync: write failed

Thats what all evidence points at, although there's just one way to be sure, run a SMART test on that disk.

Offline

Board footer