rsync - Sep 2006 - Syncing moved files

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

I use rsync to keep an off-site backup of my photographs.

I dump from my camera everything into a tmp/ directory, which I then
clean and move gradually all pictures into the right directory
(Vacations/, for example).

But rsync does not know that I moved an identical picture from tmp/ to
Vacations/, it transfers the whole file, and deletes the one that was in
tmp/, even though a local move might have done it.

Is there a way that rsync could, for all known files, sync paths instead
of file content whenever local and remote files are identical (using
sha1 or md5)?

- --
==============         +----------------------------------------------+
Martin Gadbois         | "Windows might take you from 0 to 60 faster, |
S/W Developer          |  but to go to 100 you need Unix."            |
Colubris Networks Inc. +----------------------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFE+2s9Y3/iTTCEDkRAtRCAKCkPYi9xgj+6+s6ZIX5NNaG4Xev7wCfWIsn
LQ4m0YR522cvyfEUScuL71o=KWkW
-----END PGP SIGNATURE-----

On 9/22/06, Martin Gadbois <martin.gadbois@colubris.com>
wrote:
> But rsync does not know that I moved an identical picture from tmp/ to
> Vacations/, it transfers the whole file, and deletes the one that was in
> tmp/, even though a local move might have done it.
>
> Is there a way that rsync could, for all known files, sync paths instead
> of file content whenever local and remote files are identical (using
> sha1 or md5)?
The experimental --detect-renamed option provided by the patch
"patches/detect-renamed.diff" will make rsync incrementally transfer
each moved file using the receiver's unmoved file as the basis.  That
will cut out almost all of the network traffic but will not reduce
disk I/O.  I suppose you want the receiver to skip the transfer
entirely and just move the file if --checksum is on and the checksums
match.  The patch doesn't have this behavior yet.  Someone who
understands the patch better than I do should add it.

--fuzzy and --detect-renamed are very similar; they just consider
different sets of potential basis files.  Perhaps their
implementations should be merged.

Matt