Mapped Drive

Stephen Zemlicka stevezemlicka at
Sun Sep 30 05:29:37 GMT 2007

The problem is some files don't change in size.  So I was hoping that the
checksums could be cached.  Perhaps I'm mistaken but I thought the checksum
determined what actual blocks were transferred.  I suppose it could be
cached at either storage location.

Stephen Zemlicka
Integrated Computer Technologies
PH. 608-558-5926
E-Mail stevezemlicka at 

-----Original Message-----
From: hashproduct at [mailto:hashproduct at] On Behalf Of Matt
Sent: Saturday, September 29, 2007 5:03 PM
To: Stephen Zemlicka
Cc: rsync at
Subject: Re: Mapped Drive

On 9/28/07, Stephen Zemlicka <stevezemlicka at> wrote:
> Is there a way to have rsync cache the checksums for something like this
> would that help?

I'm not sure exactly what you mean.  You said you were using the -c
(--checksum) option, which makes rsync decide whether to update each
destination file by reading the file in full and comparing its MD4/MD5
checksum with that of the source file.  Do you mean you want rsync to
cache the checksums of the destination files?  On which machine would
the cache be?

Anyway, if the issue is that you don't want rsync spending the
bandwidth to read the destination files for the --checksum check, just
remove -c and rsync will use the default size-and-mtime quick check.


More information about the rsync mailing list