View Issue Details

IDProjectCategoryView StatusLast Update
0000244RsyncBugpublic2020-08-24 03:13
Reportervenuto Assigned Topsmedley  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionunable to reproduce 
Summary0000244: Rsync failed sync with NAS server
Description[D:\]rsync -v -r -p -t -R /stalker/* nas:/mnt/Backup
sending incremental file list
rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
rsync: mkdir "D://nas:/mnt/Backup" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(596) [receiver=3.0.0pre10]
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=
3.0.0pre10]
TagsNo tags attached.

Activities

psmedley

2008-05-05 09:47

administrator   ~0000854

OK I can reproduce this - now need to work out why it happens

psmedley

2008-05-05 09:58

administrator   ~0000855

Current drive letter is prepended in function full_fname() - clearly rsync thinks nas:/mnt/Backup is a file path not a URL

psmedley

2010-07-31 10:24

administrator   ~0001680

Please test with Rsync 3.0.7

Issue History

Date Modified Username Field Change
2008-03-31 10:03 venuto New Issue
2008-05-05 09:47 psmedley Note Added: 0000854
2008-05-05 09:58 psmedley Note Added: 0000855
2010-07-31 10:24 psmedley Note Added: 0001680
2010-07-31 10:24 psmedley Assigned To => psmedley
2010-07-31 10:24 psmedley Status new => feedback
2011-12-31 08:18 psmedley Status feedback => resolved
2011-12-31 08:18 psmedley Resolution open => unable to reproduce
2012-12-22 17:44 Steven Levine Project Other Unix Port => Rsync
2020-08-24 03:13 psmedley Status resolved => closed