Re: Failed rsync -- two different files considered up to date
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.. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Failed rsync -- two different files considered up to date
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.. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Failed rsync -- two different files considered up to date
I hadn't thought of that one... I was going to suggest -c (--checksum). Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] Greger Cronquist writes: > I've used rsync successfully for several years, syncing between two > Windows 2000 servers using daemon mode, but today I stumbled accross > something peculiar. I'm using cygwin with rsync 2.6.0 at both ends (the > latest available at this date) and I have a file that rsync considers up > to date even though both the md5 and a normal diff show differences. > 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. > > Are there any things I should try or information that I can include? All > -vvv gives me is "uptodate". How about -I (--ignore-times)? Craig -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Failed rsync -- two different files considered up to date
Greger Cronquist writes: > I've used rsync successfully for several years, syncing between two > Windows 2000 servers using daemon mode, but today I stumbled accross > something peculiar. I'm using cygwin with rsync 2.6.0 at both ends (the > latest available at this date) and I have a file that rsync considers up > to date even though both the md5 and a normal diff show differences. > 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. > > Are there any things I should try or information that I can include? All > -vvv gives me is "uptodate". How about -I (--ignore-times)? Craig -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Failed rsync -- two different files considered up to date
Hi, I've used rsync successfully for several years, syncing between two Windows 2000 servers using daemon mode, but today I stumbled accross something peculiar. I'm using cygwin with rsync 2.6.0 at both ends (the latest available at this date) and I have a file that rsync considers up to date even though both the md5 and a normal diff show differences. 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. Are there any things I should try or information that I can include? All -vvv gives me is "uptodate". Regards, Greger -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
