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

For some reason, I'm unable to transfer *sometimes*, *some* files from a 
Windows server running rsyncd.

1. First, a try that succeeds - I want to copy "backup" directory,
which
is in "share":

$ rsync  --partial --dry-run -a -v --progress 
rsync://user@server/share/backup /tmp
Password:
receiving file list ...
30 files to consider
backup/
backup/acls-c.bat.txt
backup/acls-e.bat.txt
backup/acls-f.bat.txt
backup/acls-g.bat.txt
backup/run-backup.bat
backup/fileacl/
backup/fileacl/fileacl.exe
backup/fileacl/run-fileacl.bat
backup/shadow/
backup/shadow/CreateShadow.cmd
backup/shadow/RMTSHARE.EXE
backup/shadow/makeshadow.cmd
backup/shadow/vshadow.exe


2. But I don't need to copy the whole "/share/backup", all I
really want
to transfer is "/share/backup/fileacl" - we change the rsync command 
line accordingly:

$ rsync  --partial --dry-run -a -v --progress 
rsync://1wrckUrpGaMn@192.168.100.71/uDrive/backup/fileacl /tmp
Password:
receiving file list ...
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(1285) [sender=2.6.8]
rsync: connection unexpectedly closed (86 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(453) 
[receiver=2.6.9]


The second try fails, why? The directory I tried to copy in the second 
try was copied just fine in the first try.


I don't see any obvious problem here.


-- 
Tomasz Chmielewski
http://wpkg.org

On Mon, Dec 25, 2006 at 02:40:47PM +0100, Tomasz Chmielewski
wrote:
> 2. But I don't need to copy the whole "/share/backup", all I
really want
> to transfer is "/share/backup/fileacl" - we change the rsync
command
> line accordingly:
Why did you change the module name from "share" to "uDrive"?
That's why
one command succeeds and one fails.  The uDrive module looks to have a
bad path setting:  you can't use drive letters with rsync, so be sure to
specify something like "/cygdrive/u" instead of "u:".

..wayne..

Matt McCutchen wrote:
> On 12/25/06, Tomasz Chmielewski <mangoo@wpkg.org> 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
> configuration.
Indeed, it works when I specify "path = /cygdrive/u" instead of
"path =
u:" in rsyncd.conf - thanks a lot.


-- 
Tomasz Chmielewski
http://wpkg.org