On Wed, Nov 10, 2010 at 10:49 AM, Daniel Shahaf <d...@daniel.shahaf.name> wrote: > OSG wrote on Tue, Nov 09, 2010 at 20:58:53 -0600: >> On 11/09/2010 06:41 PM, Daniel Shahaf wrote: >> > Edward Ned Harvey wrote on Sat, Nov 06, 2010 at 20:29:18 -0400: >> >>> From: opensrcguru [mailto:opensrcg...@gmail.com] >> >>> >> >>> Today, the sync process started failing on 1 repo (all others were >> >>> unaffected) on both r/o copies at the exact same time/same revision >> >>> with errors similar to the following... >> >>> >> >>> Transmitting file data .svnsync: Base checksum mismatch on >> >>> '/path/to/file/foo/bar': >> >>> expected: 2f2e025c4c4855e7466799a877b3e23d >> >>> actual: 272214b9518d352e16e7eeceeb22f573 >> >> >> > >> > Can you compare the contents of /path/to/file/foo/bar between the master >> > and mirror, as of the last revision successfully synced to the mirror? >> Yes, I had done that and yes, the last sync'd revs were in tact and accurate. >> > > So they are textually identical? Yes.
> Can you compare their checksums to the two checksums in the error message? I hadn't yet, but I can. What is being used to perform the sum (md5/sha1/???)? >> > If you create a fresh mirror and svnsync it, from r0 to that revision, >> > does the file /path/to/file/foo/bar in the fresh mirror differ from the >> > one in the master? >> No, a resync from r0 to current does not result in any differences. >> > > Meaning, a fresh resync is successful and doesn't cause any error messages? > > Or meaning, it results in the same error messages as before? > Correct. A new/fresh resync from r0 (including the previously troubled revision) to latest completes successfully with no errors. That process was the last in my troubleshooting process and is how I worked around the problem. ------ In my case, I do not believe it to be hardware related because I had two r/o copies that exhibited the same behavior at the same rev at the same time. That is, unless there was a hardware issue on the source copy. Although possible, pretty unlikely.