On Sun, Nov 07, 2010 at 12:48:01PM -0500, Edward Ned Harvey wrote: > I do think it's a bug, but I was never able to find enough info to make it > into a bug report. I kept all the good & bad versions of the repository... > I ran the "svnadmin verify" all over the place (which is enormously time > consuming) ... svnadmin dump | svnadmin load ... Everything I can think of. > Never got any error in any way, except by repeating the svnsync from the > master.
I think it's a bug, too. We (elego) have seen this svnsync checksum error at a customer site, too. Never figured out how to reproduce it. > It's 100% consistent. I get the same checksum error, on the same file, every > time. I have a supposed "good" copy of the slave repo, at rev 4050... which > will fail every time at 4061 (or something like that)... The only > explanation I can find is a md5sum collision going undetected, and then some > larger operation has an md5sum which fails as a result. I know it's > astronomically impossible, but I can't come up with any other explanation. So you can reproduce it reliably? That's very interesting. I'd like to try to debug this. If it's possible to arrange access to your repository data please contact me off-list. Thanks. Stefan
