svnsync: Invalid diff stream: insn 3 overflows the target view, but svnadmin verify says OK

[Ji...@regulusgroup.com]

Hello Subversion users,

I have a nice, large Subversion repository, and am setting up a mirror. 
This is not my first time, I've had a couple of successes with smaller 
repositories on the same mirror server and another server which I've been 
using to test various Subversion configurations. However, I've found one 
source repository which stops svnsync at a specific revision with this 
error :

"Transmitting file data ...svnsync: Invalid diff stream: insn 3 overflows 
the target view"

The files and properties from the previous revision were successfully 
committed.

I went back and ran 'svnadmin verify' on the problem repository, but that 
command gives the repo a clean bill of health. The files even export fine. 

I ran fsfsverify.py on a copy of the repository ( not with -f, just to see 
) but it didn't come up with anything that looked like an error. I'll 
provide the output if anyone thinks it'd be useful.

The svnsync is from a 1.4 server to a 1.5 server. Both are Solaris 10 
machines, both are hosted via Apache httpd. 

The blocking revision has about 12 or so binary files, some pretty large ( 
totalling 188 MB or so, the biggest is 134,944KB ) all of which took 8 
minutes or so to export.

Any ideas or suggestions? I'm not sure we care much about that particular 
revision... we're now 15k+ revisions past that one... is there a good way 
to get svnsync past this?

Many thanks to the fine programmers who find time to contribute to 
Subversion, it rocks, this is literally the first trouble we've had with 
it, and aside from my inability to get svnsync past that revision, it 
doesn't even look like anything is wrong.

I'm not subscribed at the moment, so please make sure you cc: my address.

Thanks again,
Jimmi Hagen