I have two same files, on local machine and on remote one. Their sizes are equal, and file on local machine is newer than on remote one – but rsync still attempts to copy the file.
I invoke rsync as follows:
rsync -nv -e "ssh -p 2222" <a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="8bfef8eef9cbe3e4f8ff">[email protected]</a>:/data/file.fif data/file.fif
(if I don’t use -n option, it initiates the copy operation)
Rsync docs explicitly state that it shouldn’t be happening:
Rsync finds files that need to be transferred using a "quick check" algorithm (by default) that looks for files that have changed in size or in last-modified time.
Outputs from stat:
# remote file File: `data/fif/Skovorodko_Olga_45_raw.fif' Size: 1137551966 Blocks: 2221784 IO Block: 4096 regular file Device: fd00h/64768d Inode: 286338 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1037/ platon) Gid: ( 1047/ platon) Access: 2013-08-08 18:40:16.907581658 +0400 Modify: 2013-07-16 12:01:09.158763284 +0400 Change: 2013-07-16 12:01:09.158763284 +0400 # local file File: `data/fif/Skovorodko_Olga_45_raw.fif' Size: 1137551966 Blocks: 2221792 IO Block: 4096 regular file Device: 801h/2049d Inode: 12987232 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1005/ platon) Gid: ( 1003/ platon) Access: 2013-08-08 19:02:57.146223369 +0400 Modify: 2013-08-08 19:02:57.146223369 +0400 Change: 2013-08-08 19:02:57.146223369 +0400
Why does this happen?
UPDATE:
Doing rsync --size-only results file not being copied:
delta-transmission enabled Skovorodko_Olga_45_raw.fif is uptodate total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 14 bytes received 114 bytes 85.33 bytes/sec total size is 1137551966 speedup is 8887124.73 (DRY RUN)
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
The quick check algorithm will consider as modified any file that has different modification time or different size. So, if your destination directory has a newer version of the same file, it will be considered different, and it will be synced to the source version.
That’s the expected (and safer) behaviour. For instance, let’s suppose you have two directories, ~/src and ~/dest, each one with a foobar file. In ~/src/foobar you write “foo”, and then in ~/dest/foobar you write “bar”. Now you rsync ~/src to ~/dest. What would you expect?
Both files have the same size, but the one in ~/dest is newer. Rsync standard behaviour is to replace ~/dest/foobar with ~/src/foobar. Of course, the files could be identical and it would be unnecesary, but there is no way to know that, unless you do a checksum or compare bit per bit.
If you don’t want that behaviour, that is to say, you want newer files in the receiver to be preserved, you have to use the -u (–update) flag.
-u, –update
This forces rsync to skip any files which exist on the destination and have a modified time that is newer than the source file. (If an existing destination file has a modification time equal to the source file’s, it will be updated if the sizes are different.)
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0