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

checksum problem

From: Scott Harger <scott.harger_at_pinpointinsight.com>
Date: 2005-10-26 21:04:37 CEST

We recently converted from CVS to Subversion and are having intermittent problems with our repository. We'd appreciate any suggestions help us resolve them.

We run Subversion 1.1.4 on Red Hat and have Red Hat and Windows clients. We use the apache module to access the repository over https.

Initially we used cvs2svn to load a bdb backed repository. At various times we are unable to check out certain directories in the repository. After waiting a while (or perhaps a reboot) we can then check out the same directory fine. Also, while we are in this state "svnadmin dump" fails with the following type of error message:

svn: Checksum mismatch while reading representation:
   expected: 69123b311ffba600abadb4e08478e8fd
     actual: 038044a1bd093f747958fad16b99807a

I have noticed that while in this state if I download certain files through the web browser interface (they are typically 10-20M zip files) they appear to be truncated and do not match the same file from a directory that was previously checked out successfully.

While in this state I can dump early versions of the repository (say < revision 500) but for revisions after that I am unable to and get the checksum errors. Again, after a reboot or some undetermined time period this behavior can go away and I can checkout and dump without issue and the files accessed through the web interface are correct.

When we can't checkout a directory our svn error log frequently has messages like this:

[Sun Oct 23 22:42:24 2005] [error] [client] Provider encountered an error while streaming a REPORT response. [500, #0]
[Sun Oct 23 22:42:24 2005] [error] [client] A failure occurred while driving the update report editor [500, #160004]
[Sun Oct 23 22:42:24 2005] [error] [client] Checksum mismatch on rep '2a46':! expected: 2ee6c00158c39537f8db1c5bf771d4ec! actual: 45a9d3f50b5fd1d0397fd1b2a199c308! [500, #160004]

Also we've seen things like this a couple times:

[Thu Oct 13 02:04:23 2005] [error] [client] Reference to non-existent node 'dg3.0.tx' in filesystem '/svn/dev/db' [500, #160014]

I have run svnadmin recover after seeing these kinds of messages, and that has helped some. But it doesn't seem to do anything for the intermittent checksum errors.

To eliminate bdb as a cause of our problems, we created a fsfs backed repository and loaded it with a dump of the latest revision from the bdb repository (a dump created during one of those times that it could run successfully without the checksum errors)

Sadly we are still seeing the weird behavior with the fsfs backed repository in that we cannot check out certain directories at certain times. From the error log:

[Wed Oct 26 11:00:10 2005] [error] [client] Provider encountered an error while streaming a REPORT response. [500, #0]
[Wed Oct 26 11:00:10 2005] [error] [client] A failure occurred while driving the update report editor [500, #160004]
[Wed Oct 26 11:00:10 2005] [error] [client] Checksum mismatch while reading representation:! expected: 229bd9f706e9c459074504e381e9b749! actual: 5ef38f74f814a76f6fc7c66c66800c45! [500, #160004]


Received on Wed Oct 26 22:08:25 2005

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.