Hi Henry, We seam to have managed to get it to behave itself now. I'm not sure, but the drive may have been formatted with an MBR as appose to a GUID partition table. We've repartitioned the drive, done some updates and a reboot on the machine and it seams to be behaving itself ok now.
Regards, Michael On 2/06/2013, at 11:37 PM, henri wrote: > Hello, > >> This is showing up for one of our backup systems: >> >> ================================================================= >> >> Using custom rsync : v3... >> Preservation of ACL's disabled >> Synchronizing... >> rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken >> pipe (32) >> rsync: connection unexpectedly closed (4448632 bytes received so far) >> [sender] >> rsync error: error in rsync protocol data stream (code 12) at io.c(601) >> [sender=3.0.8] >> >> WARNING! : Data Transfer Interrupted >> >> ================================================================= >> >> This seams to be happening when we're trying to do the first run, full copy >> of a backup. We have another backup drive that's only doing incremental >> backups that are working fine. The new backup drive is a brand new drive and >> has been tested ok. >> >> The computer is running a custom compiled version of rsync (version 3.0.9) >> and Mac OS X "Server" Lion (10.7.3). >> >> Has anyone got any ideas what is going on with this? > > I have a few questions : > > (1) Is the destination a local HDD or SSD? > (2) Is the source accessed locally or is it accessed via the network? > (3) How large is the source for this copy? > (4) Is there anything being excluded from the backup (data in the excludes > file)? > > Thanks. > Henri > > > > _______________________________________________ > lbackup-discussion mailing list > http://www.lbackup.org > > Change options or unsubscribe : > http://lbackup.org/mailing_lists > _______________________________________________ lbackup-discussion mailing list http://www.lbackup.org Change options or unsubscribe : http://lbackup.org/mailing_lists
