no such file or directory - but hey, the files are there!

Matt McCutchen hashproduct+rsync at
Tue Dec 26 03:44:46 GMT 2006

On 12/25/06, Tomasz Chmielewski <mangoo at> wrote:
> [...]
> rsync: pop_dir "/cygdrive/c/WINDOWS/system32/u:" (in uDrive) failed: No
> such file or directory (2)
> rsync error: errors selecting input/output files, dirs (code 3) at
> flist.c(1281) [sender=2.6.9]
> rsync: connection unexpectedly closed (445 bytes received so far) [receiver]
> rsync error: error in rsync protocol data stream (code 12) at io.c(453)
> [receiver=2.6.9]
> Note that it should be successful, as the directory exists above in the
> example 1, and did copy fine?

The gist is that rsync cannot handle paths like "u:".  On the first
command, rsync got lucky and worked anyway because the root of the
transfer happened to be the root of the module.  As Wayne said, you
should specify "/cygdrive/u" instead of "u:" in the module


More information about the rsync mailing list