Rsync Tossing Errors

Osiris990 · 07-29-2009, 03:59 PM

I'm trying to setup an off-site backup server using rsync to sync up incremental backups. Development was going fine until a couple hours ago when I attempted to sync a single, unaltered file against the remote copy. (~13 GB) The program is now dumping the following error and failing to sync when I try to sync that file:

Quote:

[nia@NIA-BDR001 SBS]$ ./test.sh
Wed Jul 29 15:39:18 CDT 2009
Rsync initiated.

Password:
Backup.bkf
rsync: writefd_unbuffered failed to write 1 bytes [sender]: Broken pipe (32)
rsync error: timeout in data send/receive (code 30) at io.c(171) [receiver=2.6.8]
rsync: connection unexpectedly closed (100 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [generator=2.6.8]
rsync: connection unexpectedly closed (956202 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [sender=2.6.8]
Wed Jul 29 15:51:26 CDT 2009
[nia@NIA-BDR001 SBS]$

For those curious, test.sh contains the following script:

Quote:

#!/bin/bash
date
rsync --verbose -z Backup.bkf nia@IP.AD.DR.ESS::nia
date

It doesn't do it for any other files, and when I deleted and rsync'd the file again, it went fine. It only throws this error when I attempt to sync that one file.

Any ideas what's going on?

colucix · 07-30-2009, 08:53 AM

What if you try without the -z option? I suspect it is a problem with file compression, rather than with the transfer process.

Osiris990 · 08-03-2009, 09:10 AM

Quote:

Originally Posted by colucix

What if you try without the -z option? I suspect it is a problem with file compression, rather than with the transfer process.

Good thinking, that was the culprit. Why was that causing the problem, though? That doesn't really make any sense to me, considering how the algorithm works. (or at least my understanding of the algorithm, which might be flawed)