Failed rsync -- two different files considered up to date
Greger Cronquist
greger_cronquist at yahoo.se
Tue Mar 30 06:29:34 GMT 2004
Thank you all!
After some further, rather ugly, investigation it turned out that the
original files (we found three of them!) had been corrupted by Windows.
A fact I'm going to but in my growing pile of arguments for switching to
a real operating system, at least for our servers. With that out of the
way, rsync performed flawlessly.
/Greger
Wayne Davison wrote:
>On Mon, Mar 29, 2004 at 06:09:28PM +0200, Greger Cronquist wrote:
>
>
>>I've tried calling rsync with several different options, most notably -c
>>for forcing checksum, but it fails to see a difference between the files.
>>
>>
>
>If -c failed to notice that the files are different, then either (1) the
>MD4 checksums accidentally match (rare, but not impossible), or (2) your
>double-check accidentally compared the wrong files.
>
>One way to force a resend is to touch the source file and then use
>--whole-file to ensure that you get a complete re-copy without any
>accidental block matches.
>
>..wayne..
>
>
More information about the rsync
mailing list