radius13a at mac.com
Fri Oct 12 17:02:27 GMT 2007
Thanks. I'll take a look at this starting next week. I do realize
this is very risky. ;)
The other option I thought of was to only do the move when the mtime,
size, and filename match. Not really a 'detect-renamed' but a
'detected-moved' type operation.
On Oct 12, 2007, at 9:55 AM, Matt McCutchen wrote:
> On 10/11/07, radius13a at mac.com <radius13a at 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.
More information about the rsync