I asked a question about not link-dest not creating hardlinks and got ideas and hints that led to the solution which is the link-dest dir must/should be relative to the destination and/or the destination must be empty. I did both and that works fine.

My question is what would cause rsync to copy a file that has not changed. I can tell link-dest is working because about 8.5 GB of 40 GB were transfered. My command:

  rsync --log-file=/share/data/rsync.log  -vvaxH --numeric-ids --delete \
     --exclude=/home/apache/logs --link-dest=../../../201003/newharbor/home/ \
     -e ssh r...@newharbor.safeport.com:/home .

In checking inodes I can find many files that did not change on the server. E.g.:

artemis:/mnt# diff 201003/newharbor/home/allvid/allvid.tgz 
201007/newharbor/home/home/allvid/allvid.tgz
artemis:/mnt# ls -il 201003/newharbor/home/allvid/allvid.tgz
146490838 -rw-r--r-- 1 root 2174 70764 Oct 8 2008 201003/newharbor/home/allvid/allvid.tgz
artemis:/mnt# ls -il 201007/newharbor/home/home/allvid/allvid.tgz
151176421 -rw-r--r-- 2 root 2174 70764 Oct 8 2008 201007/newharbor/home/home/allvid/allvid.tgz

Thanks for any ideas.

_____
Douglas Denault
http://www.safeport.com
d...@safeport.com
Voice: 301-217-9220
  Fax: 301-217-9277
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Reply via email to