Version-Release number of selected component: rdiff-backup-1.2.8-11.fc20 Additional info: reporter: libreport-2.2.3 cmdline: /usr/bin/python /usr/bin/rdiff-backup -v5 --force --print-statistics /g8/3.videos 192.168.0.254:://g8/3.videos executable: /usr/bin/rdiff-backup kernel: 3.15.10-200.fc20.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: log.py:136:log_to_term:IOError: [Errno 5] Input/output error Traceback (most recent call last): File "/usr/bin/rdiff-backup", line 30, in <module> rdiff_backup.Main.error_check_Main(sys.argv[1:]) File "/usr/lib64/python2.7/site-packages/rdiff_backup/Main.py", line 310, in error_check_Main Log.FatalError(errmsg) File "/usr/lib64/python2.7/site-packages/rdiff_backup/log.py", line 160, in FatalError self.log_to_term(prefix_string + message, 1) File "/usr/lib64/python2.7/site-packages/rdiff_backup/log.py", line 136, in log_to_term termfp.write(self.format(message, self.term_verbosity)) IOError: [Errno 5] Input/output error Local variables in innermost frame: termfp: <open file '<stderr>', mode 'w' at 0x7fc0581601e0> message: 'Fatal Error: Killed with signal 1' verbosity: 1 self: <rdiff_backup.log.Logger instance at 0x7fc04fa09cf8> Potential duplicate: bug 1005543
Created attachment 931069 [details] File: backtrace
Created attachment 931070 [details] File: environ
Looks like it's unable to open it's main log for writing. Can you provide: df /g8/3.videos(on backup host) df -i /g8/3.videos (on backup host) ls -laZ /g8/3.videos/rdiff-backup-data/backup.log findmnt /g8/3.videos
Sure, although I am not sure if they are valid any longer. > df /g8/3.videos(on backup host) Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/vg_ivy-g8 850074204 621697824 185195120 78% /g8 > df -i /g8/3.videos (on backup host) Filesystem Inodes IUsed IFree IUse% Mounted on /dev/mapper/vg_ivy-g8 53977088 192049 53785039 1% /g8 > ls -laZ /g8/3.videos/rdiff-backup-data/backup.log -rw------- 1 pevogam pevogam ? 211798 Aug 26 23:24 /g8/3.videos/rdiff-backup-data/backup.log > findmnt /g8/3.videos <empty>
Any errors in dmesg on that server? What filesystem type is /g8? Does the problem persist if you re-run the backup?
> Any errors in dmesg on that server? No, not really, although: [pevogam@seven ~]$ sudo cat /var/log/messages | grep rdiff Aug 26 16:00:18 seven python: detected unhandled Python exception in '/usr/bin/rdiff-backup' Aug 26 16:00:18 seven python: detected unhandled Python exception in '/usr/bin/rdiff-backup' > What filesystem type is /g8? ext4 on top of LVM > Does the problem persist if you re-run the backup? I had troubles with a file where it stopped but removing it from the backup and then adding it back (second backup run) helped.
ok, my only other guess here is that it could have been a transitory network failure. Are the two machines on the same local network?
Yes they are, although even a network failure is not supposed to lead to a crash but I guess that's all we've got for this information. There is nothing else which is exotic configuration that I can think of.
I see one mention of this error when it was a drive issue... remapping bad blocks was confusing rdiff-backup: http://www.linuxquestions.org/questions/linux-software-2/rdiff-backup-[errno-5]-input-output-error-887133/ might be worth trying a fsck.ext4 -c on the drive if you are able and see if it finds anything?
Unfortunately I don't have the previous setup and it all works well now. The drives are completely new, so a drive issue might be an overkill. I guess we might wait for it to reoccur or close it.
ok. Please let me know if you see it again... thanks.