[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Checksum mismatch creating repository?

From: Arivan S. Bastos <asbastos.br_at_gmail.com>
Date: Thu, 8 Jul 2010 19:28:05 -0300

Hello,

We work with Subversion for about two years here in the company, with no
trouble.
We have already used the subversion server on a Windows XP and on Windows
Server 2008.

This week, the disk of our server burned and then we decided to upgrade the
windows
2008 server to Windows Server 2008 R2.

After the upgrade we are facing problem with the use of Subversion.
We try to use VisualSVN 2.1.2 and CollabNet 1.6.12, and also tried going
back to version 1.4.6
(the version we used before the OS update), but always facing the same
error:

"error: svn: Checksum mismatch for #FILENAME#"

The error happens when creating the repository using the command "svn
import" to add, and
always seems to occur in large files over 100Mb. If we insist on trying to
send the file, sometimes it is sent.
However, when trying to perform the checkout (on client side) we got"cannot
read chunk size"
somewhere in the checkout, and looking at the apache log, we see the same
"Checksum mismatch".

Using the same version of subversion, performing the same procedures on the
same files on a
computer running windows 7, this error does not occur.

It seems that there is some limitation of use of resources, because this
seems to happens with large files only.
I searched a lot for this error, but the cases I encounter are repositories
damaged, appeared not to
be the case because we are creating the repository, and can perform this
procedure on Windows 7 with no troubles!

Please, we need help!

Our enviroment
----------------------
OS: Windows Server 2008 R2

Attempt 1) Visual SVN Server 2.1.2
Attempt 2) CollabNet Subversion 1.6.12 + Apache 2.2.15
Attempt 3) Subversion 1.4.6 + Apache 2.2.15

Thank you
Received on 2010-07-09 00:29:46 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.