rsync failure on corrupted source data

Fabian Cenedese Cenedese at
Tue Jun 28 06:18:59 UTC 2016

At 05:55 28.06.2016, Paul J. Durack wrote:

>I am trying to copy data from a partially corrupt backup (time machine) disk on a os x system to another.
>And am getting the following error:
>Backups.backupdb/durack1ml/2016-02-10-091749/durack1ml_hdd/Applications/Adobe Media Encoder CC 2015/Adobe Media Encoder CC
>rsync: writefd_unbuffered failed to write 14550 bytes [sender]: Broken pipe (32)
>rsync: write failed on "/Volumes/durack1ml_bak/160405_1234/Backups.backupdb/durack1ml/2016-02-10-091749/durack1ml_hdd/Applications/Adobe Media Encoder CC 2015/Adobe Media Encoder CC": Result too large (34)
>rsync error: error in file IO (code 11) at /BuildRoot/Library/Caches/ [receiver=2.6.9]
>rsync: connection unexpectedly closed (14352612 bytes received so far) [sender]
>rsync error: error in rsync protocol data stream (code 12) at /BuildRoot/Library/Caches/ [sender=2.6.9]
>Is there a way to get rsync to continue when such an error is encountered?

Are you sure that the problem is with the corrupted source data? Because the
error happens on writing the data on the destination.

rsync: write failed on ... : Result too large (34)

However I don't know what that error means.

bye  Fabi

More information about the rsync mailing list