I'm attempting to use Rsync (2.4.3) to update files between a Linux server, 
and a Linux client with a mounted vfat partition (/c). I've heard about the 
problem where windows mtime's arn't 100% accurate to the second, and 
noticed that myself, but I'm not totally sure if vfat in linux mimics that 
problem or not. I highly doubt it though.

The problem is this. If I run rsync with the following command:

rsync -rptS --timeout=240 --stats --delete --exclude-from=exclude.lst 
[EMAIL PROTECTED]::sync/ /c/

It takes approx. 18minutes on a Celeron 333a 64mb ram client, same only 
128mb ram server to complete the task. When using full verbose (-vvvv ) I 
notice that rsync is calculating checksums for virtually every file if not 
every file. (25,000 files, 1.5 gb's about) If I run the above line twice in 
a row, one right after another (obviously no files have changed) it _still_ 
calculates checksums.

The weird part is this.

rsync -rptS --timeout=240 --stats --delete --exclude-from=exclude.lst 
[EMAIL PROTECTED]::sync/windows /c/windows

If I run the above line, (just update the windows directory) the first time 
it runs, all the checksums are calculated, (240megs or so) If I run it 
again, immediately after, its completed in about 5seconds, no checksums are 
calculated at all. (this is how it should be, correct?)

So why when I try to update the entire exported directory (or share, which 
ever you want to call it?) at once (::sync/ /c/), it calculates the 
checksums for every file, every time its run regardless, but if I just do 
one directory at a time(::/sync/windows /c/windows/), it seems to work the 
way it should? Thanks. 

Reply via email to