Checksum mismatch error becoming critical

After convincing my boss (and myself) that SVN would be a good replacement
for his older revision control system we are now having second thoughts. Our
company produces multimedia applications for pharmaceutical companies (some
of which have expressed an interest in using SVN internally and we have lots
of large binary files and very tight deadlines. We recently upgraded our
server to a quad Xeon running Red Hat 7 and we have an svnserve server
version 1.1.4 that was compiled with the –enable-all-static flag and is
using Berkeley DB 4.2.52. We have all of our repositories under a single
directory. Lately we have been getting a lot checksum mismatch errors when
we do an update on our working copies. I went and did a “svnadmin verify” on
the corresponding repositories and they come up clean (no checksum errors in
the repository). I would like to use the SVN module under Apache 2 but since
our server is outsourced the hosting company will not allow us to install it
since they only support Apache 1.32. Basically I am stuck with svnserve. I
am quickly running out of options here and my boss is understandably
irritated with this issue. I have done several experiments where I can check
out projects locally on the server with no problems. The issue appears to
occur randomly when we do frequent updates on our working copy using
TortiseSVN. I need to find some sort of solution soon or we will have to
pull SVN out of our production pipeline and revert back to our old
system…which would suck. My question is has anyone run svnserve on a machine
with multiple processors? How about a quad system? Is the OS too old?

Thanks,

Rob.

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.322 / Virus Database: 266.11.16 - Release Date: 5/24/2005