|
From: | Pavel Raiskup |
Subject: | Re: [Help-tar] tar on Fedora to Drobo failing with Cannot close: Input/output error /bin/tar: Exiting with failure status due to previous errors |
Date: | Mon, 27 Feb 2017 18:10:43 +0100 |
User-agent: | KMail/5.3.3 (Linux/4.9.10-200.fc25.x86_64; KDE/5.29.0; x86_64; ; ) |
On Monday, February 27, 2017 11:49:54 AM CET Robert Kudyba wrote: > This happens on 1 Fedora 25 workstation backing up a tar to a Drobo NAS. > ERROR OUTPUT: > /bin/tar: /ourserver/etc-new.tgz: Cannot close: > Input/output error > /bin/tar: Exiting with failure status due to previous errors The 'close()' syscall returned non-zero value and errno was set to EIO That sounds like some underlying issue with your hardware. > in dmesg I do see occasional errors like this: > > [Mon Feb 27 01:13:19 2017] CIFS VFS: Error -11 sending data on socket to > server > [Mon Feb 27 01:46:41 2017] CIFS VFS: Server ourdrobo has not responded in 120 > seconds. Reconnecting... This might be related (I'm not familiar with your hardware/setup) if CIFS is used to support your hardware. It is unlikely tar would be able to recover from such issues if no underlying layer does so. I would be cautious to ignore such issue as your backup might be incomplete. So failing the whole backup process makes sense to me. Pavel
[Prev in Thread] | Current Thread | [Next in Thread] |