running: 'rsync -av 2010-old /Volumes/coltrane/test-transfer/' from my 'Photos directory, about 980 files moved and then I got this:
###################################################################### ... bunch of stuff before this.... 2010-old/Halloween Workshop with Bob and Mary/aws-20101016x21152402-01.cr2 2010-old/Halloween Workshop with Bob and Mary/aws-20101016x21155143-01.cr2 rsync: writefd_unbuffered failed to write 32768 bytes [sender]: Broken pipe (32) rsync: write failed on "/Volumes/coltrane/test-transfer/2010-old/Halloween Workshop with Bob and Mary/aws-20101016x21155143-01.cr2": Bad file descriptor (9) rsync error: error in file IO (code 11) at /SourceCache/rsync/rsync-40/rsync/receiver.c(268) [receiver=2.6.9] rsync: connection unexpectedly closed (35488 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at /SourceCache/rsync/rsync-40/rsync/io.c(452) [sender=2.6.9] ###################################################################### Running, 'ls -la |grep aws-20101016x2115' in the local source directory, I get: -rw-rw-rw-@ 1 alans staff 7469886 Oct 17 2010 aws-20101016x21152402-01.cr2 -rw-rw-rw-@ 1 alans staff 11520662 Oct 17 2010 aws-20101016x21155143-01.cr2 -rw-rw-rw-@ 1 alans staff 11721658 Oct 17 2010 aws-20101016x21155870-01.cr2 And on the EON volume, I get: -rwx------ 1 alans staff 2342912 Apr 17 19:28 .aws-20101016x21155143-01.cr2.rhlJTG -rwx------ 1 alans staff 7469886 Oct 17 2010 aws-20101016x21152402-01.cr2 ###################################################################### Once again, if I just reissue the rsync command, it picks up from where it left off and moves the problem file over just fine. Running ls -la on the eon directory I now get: -rwx------ 1 alans staff 2342912 Apr 17 19:28 .aws-20101016x21155143-01.cr2.rhlJTG -rwx------ 1 alans staff 7469886 Oct 17 2010 aws-20101016x21152402-01.cr2 -rwx------ 1 alans staff 11520662 Oct 17 2010 aws-20101016x21155143-01.cr2 -rwx------ 1 alans staff 11721658 Oct 17 2010 aws-20101016x21155870-01.cr2 So, the dead file is still there, but the fresh working copy is all set. ###################################################################### Now here's the weird thing.... This all happened while going over a 1GB ethernet connection. However, when I disconnect the cable on the Mac and run the rsync over wireless, it doesn't appear to have an issue. I let it run for several hours and it never choked. I'm not going to do a lot of testing on that at this point, but I would have expected it to fail rather quickly as well. I'm sure that the total number of files sent over the slower wireless was well beyond where the wired connection usually fails. The wireless was plugging along nicely until I killed it so I could do a little more testing. Other things that I've done: * Mac to firewire dirve rsync - No issues. * Mac to a windows network share drive - No issues. So, at this point, it looks like the issue is only occurring when I'm writing to the eon server over the 1GB ethernet. Next up, I'm going to try the updated rsync client for the Mac to see if that works better. Just wanted to put this in as a status update in the mean time. -- This message posted from opensolaris.org _______________________________________________ distribution-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/distribution-discuss
