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

RE: checksum mismatch error - how to rectify?

From: Johan Corveleyn <johan.corveleyn_at_uz.kuleuven.ac.be>
Date: Mon, 7 Sep 2009 17:53:26 +0200

> Van: Maróy Ákos [mailto:akos_at_maroy.hu]
>
> Hi,
>
> I'm encountering a problem with my subversion repository. On svn
> updates, I get from the client side:
>
> $ svn update
> svn: REPORT of '/corpora/!svn/vcc/default': Could not read chunk
> delimiter: Secure connection truncated
> (https://svn.doublenegatives.jp)
>
>
> at the same time, I see the following in the apache log:
>
> [Fri Sep 04 05:40:49 2009] [error] [client 67.148.95.116] Provider
> encountered an error while streaming a REPORT response. [500, #0]
> [Fri Sep 04 05:40:49 2009] [error] [client 67.148.95.116] A failure
> occurred while driving the update report editor [500, #160004]
> [Fri Sep 04 05:40:49 2009] [error] [client 67.148.95.116] Checksum
> mismatch while reading representation:\n expected:
> a891e6ac1d4b8f780a0df90f82885e54\n actual:
> 5e628980411449c4447440919432587b\n [500, #160004]
>
>
> I run svnadmin verify on the repository, and I get:
>
> $ svnadmin verify /var/svn/doublenegatives.jp/repos/corpora
> * Verified revision 0.
> * Verified revision 1.
> * Verified revision 2.
> ...
> * Verified revision 31.
> * Verified revision 32.
> svnadmin: Checksum mismatch while reading representation:
> expected: a891e6ac1d4b8f780a0df90f82885e54
> actual: 0e97b329651c3632dc6de1f978da3d21
>
>
> I run fsfsverify on changeset 33, and it doesn't report any issues.
>
> How can I get out of this situation?

Hm, I'm no expert on fsfsverify or repository corruption, but I remember having read a couple of times on this mailinglist that you may have to run it multiple times to repair the corrupted revision. After that, try svnadmin verify again to see if it's fixed or not.

Maybe you can start by searching the mailinglist archives for fsfsverify, so you can read about other people's experiences. Or even a google search for fsfsverify and/or corrupted svn repository.

Other than that, you should investigate why your repository got corrupted in the first place (disk problem? Some bad file manipulation? Someone did a recursive search/replace in the wrong place? ...). Maybe you can just replace the corrupted revision file from a backup?

Regards,
Johan

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2391978

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-07 17:54:31 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.