rsync - Oct 2007 - --detect-renamed question

I've started testing the detect-renamed patch with 2.6.9 and soon 3.0.0pre1.
I have an unique situation where I'm rsync'ing to a HSM based
filesystem.  I've found that the detect-renamed patch works but it appears
to do a copy of the file to the new destination.  This is particular slow since
the file in the HSM based filesystem may only be a stub and all the data is only
resident on tape.  The copy waits for the datq to be recalled from tape which
depending on the file size can take a long time.  I've looked through the
patch code and am wondering if there is an easy way to have rsync do a move from
the ~.tmp. directory.

thanks,
Greg

On 10/11/07, radius13a@mac.com <radius13a@mac.com>
wrote:
> I've started testing the detect-renamed patch with 2.6.9 and soon
3.0.0pre1.  I have an unique situation where I'm rsync'ing to a HSM
based filesystem.  I've found that the detect-renamed patch works but it
appears to do a copy of the file to the new destination.  This is particular
slow since the file in the HSM based filesystem may only be a stub and all the
data is only resident on tape.  The copy waits for the datq to be recalled from
tape which depending on the file size can take a long time.  I've looked
through the patch code and am wondering if there is an easy way to have rsync do
a move from the ~.tmp. directory.
This is easy to do, and I have implemented a --trust-detect-renamed
option to do it in the attached patch to the current CVS rsync.
However, it is risky because a false rename detection could cause
rsync to substitute an unrelated but similar-looking destination file
for a new source file.  Don't use the option unless you are prepared
for the consequences.

Matt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: trust-detect-renamed.diff
Type: text/x-patch
Size: 5006 bytes
Desc: not available
Url :
http://lists.samba.org/archive/rsync/attachments/20071012/88952510/trust-detect-renamed.bin