LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   performance issue: rsync sends existing files (https://www.linuxquestions.org/questions/linux-networking-3/performance-issue-rsync-sends-existing-files-261613/)

microtim 12-02-2004 01:44 AM

performance issue: rsync sends existing files
 
I've read that rsync copies only files that have been changed but I have had no success taking advantage of this feature. Instead, rsync always copies every file whether or not it already exists. For example, I have a bunch of avi files. I run...

% rsync -avz /vidz uid@dest:/vidz

This copies all files to the destination machine. Then I run that exact same command. The second run takes just as long as the first run.

The owner of and permissions of the files are exactly the same on both the source and destination. I don't understand why rsync determines that the entire file should be sent.

Below is my rsyncd.conf. Can anyone help? Thanks in advance. -Tim

log file = /var/log/rsyncd.log
pid file = /var/run/rsyncd.pid
lock file = /var/run/rsync.lock

[bling]
path = /home/microtim/bling
comment = Laptop backup
uid = microtim
gid = users
read only = no
list = yes
secrets file = /etc/rsync/rsyncd.scrt
auth users = microtim

[Pictures]
path = /home/microtim/Pictures
comment = My Pictures
uid = microtim
gid = users
read only = no
list = yes
secrets file = /etc/rsync/rsyncd.scrt
auth users = microtim

microtim 12-02-2004 02:27 AM

problem solved !! [6 months later]
 
totally friggin weird!! On the source-end, I set all files to be readable (744) and that solved the problem!! So if I rsync that .avi file once, it flies right thru the second execution. Sweet.

This is how I figured out the problem. Upon closer examination, I found that the destination files all contained a timestamp of whatever `date` prints outs, or today. For a mirroring tool like rsync, this didn't make sense. So set readability for a sample file and as a result, the timestamp on the destination reflected the timestamp on the source. And on the 2nd execution, rsync was able to determine that the file should not be sent.

As for why this happens, I have no clue!! I'm so curious because I spent 6 disappointing months scratching my head. -Tim


All times are GMT -5. The time now is 01:48 AM.