RE: RE: Broken repository. svnadmin verify and dump report a checksum mismatch.

After 3 days of testing and many rebuilt repositories, I still consistently
receive the Checksum mismatch error. It occurs after making a commit
containing a large zip file (434MB). The other critera is that the commit is
made from a computer other than the server. If I commit the same file from a
WC on the server itself, then the commit works fine.

Also on more than one occasion I've made a successful commit containing
moderately sized binaries (20->30MB). Then after a few subsequent commits
are made, the checksum mismatch error suddenly crops up for the revision
containing the binaries! E.g, commit large binary in revision 60. Checkout
of rev60 works fine. Commit some change in revision 61. Now suddenly
svnadmin gives a checksum error on revision 60!

My server is a dual CPU, RAID 1 setup. I have run chkdsk and had no
problem.s I run other DB apps (MSSQL and MySQL) and haven't had any
problems. The windows event viewer doesn't report any issues.

Please help. I really don't want to, but pretty soon I feel I am going to
have to abandon subversion. It's a great product, but I simply can't trust
it with our livelihood unless I can resolve this issue.

Thanks,
John

-----Original Message-----
From: John Savage [mailto:JSavage@data-mate.com]
Sent: 10 January 2006 12:51
To: users@subversion.tigris.org
Subject: RE: RE: Broken repository. svnadmin verify and dump report a
checksum mismatch.

I have only ever used TortoiseSVN as the client. I find it hard to see how a
client can cause a checksum error on the server-maintained repository.
Surely either
A) Checksums are calculated by the server and hence the client has no access
to this checksum in order to be able to cause it to get corrupted
or
B) Checksums are calculated on the client but checked on the server and
rejected if erroneous before being fully committed in the interest of
maintaining repository integrity.

I'd be very surprised if both A and B are false owing to the fact that
data-integrity is a top priority for SVN, and this appears to me as an
obvious hole in maintenance of that integrity.

Thanks for the feedback Stefan.

John

-----Original Message-----
From: Stefan Lutz [mailto:stefan.lutz@cairos.com]
Sent: 10 January 2006 12:30
To: John Savage; users@subversion.tigris.org
Subject: RE: RE: Broken repository. svnadmin verify and dump report a
checksum mismatch.

AFAIK it may be a problem of Tortoise. Some users herein ths mailing list
have reported repository problems with Tortoise as the client and (!) the
root of the problem. I am not sure if there are any other clients for a
subversion repository but if have you ever tried one?

Yours,

Stefan
--------- Fidelity in Tracking! ---------

Stefan Lutz
R & D

Cairos technologies AG
Münchener Straße 101B / Geb. 5
D-85737 Ismaning

> -----Original Message-----
> From: John Savage [mailto:JSavage@actionpoint.ie]
> Sent: Saturday, January 07, 2006 4:22 AM
> To: users@subversion.tigris.org
> Subject: RE: Broken repository. svnadmin verify and dump
> report a checksum mismatch.
>
> Apologies for not keep the last reply on the list. I had meant to, but
> suffered a quick bout of dumb thumbs!!
>
> I've tried finding info on this problem on this newsgroup,
> google and google
> groups and more or less came up empty everywhere, so if anyone has any
> feedback on my issue, it could be a great resource for anyone else
> experiencing the same problem ;).
>
> All the broken revisions were made by one person. But, that
> same person has
> made about 30% of all revisions. Also, the one working
> revision that sits in
> the middle of the four broken ones (#41) was made by that
> same user. So it
> is unlikely that it is a user issue.
>
> The SVN client is TortoiseSVN 1.2.4484 (we use the special
> compile with the
> _SVN folder hack for VS.Net web projects). There are only two
> developers. We
> both use this client and so far, I know we have never accessed the
> repository concurrently.
>
> The first broken revision (#39) IS significantly larger than the
> predecessors, but isn't the largest. It contains a commit of
> a very large
> zip file. A complete directory listing of all the files in the db/revs
> folder is as follows. I have added an asterisk to the right
> of each of the
> four broken revisions.
>
> Finally, some extra notes. I can retrieve the entire
> repository log without
> any problems. I can svnadmin dump --incremental all revisions
> except the
> four broken one and have used the dumped revision details to
> reload the good
> revisions into a fresh repository. For now, this is a barely
> acceptable
> workaround. A full recovery of the entire repository would
> obviously be more
> desirable if possible. Do you have any ideas of possible causes?
>
>
> Thanks,
> John
>
> ----------------
> 12/05/2005 02:30 AM 115 0
> 12/05/2005 02:30 AM 23,217,595 1
> 12/05/2005 02:30 AM 28,793 2
> 12/05/2005 02:30 AM 10,665 3
> 12/05/2005 02:30 AM 8,594 4
> 12/05/2005 02:30 AM 8,542 5
> 12/05/2005 02:30 AM 2,667 6
> 12/05/2005 02:30 AM 2,678 7
> 12/05/2005 02:30 AM 10,240 8
> 12/05/2005 02:30 AM 4,117 9
> 12/05/2005 02:30 AM 8,081 10
> 12/05/2005 02:30 AM 8,053 11
> 12/05/2005 02:30 AM 27,536 12
> 12/05/2005 02:30 AM 49,944 13
> 12/05/2005 02:30 AM 89,731 14
> 12/05/2005 02:30 AM 42,768 15
> 12/05/2005 02:30 AM 695 16
> 12/06/2005 11:56 AM 213,068,265 17
> 12/06/2005 12:29 PM 1,144,538,164 18
> 12/06/2005 04:55 PM 54,353,158 19
> 12/07/2005 01:38 PM 13,466 20
> 12/07/2005 01:39 PM 3,108 21
> 12/07/2005 01:40 PM 10,025 22
> 12/12/2005 11:17 AM 2,963 23
> 12/12/2005 11:59 AM 608 24
> 12/12/2005 11:59 AM 910 25
> 12/12/2005 12:00 PM 699 26
> 12/12/2005 12:00 PM 954 27
> 12/12/2005 12:04 PM 473 28
> 12/12/2005 12:12 PM 713 29
> 12/15/2005 06:07 PM 53,606 30
> 12/19/2005 12:45 PM 8,395 31
> 12/19/2005 12:46 PM 10,188 32
> 12/19/2005 05:33 PM 1,264,598 33
> 12/19/2005 06:24 PM 251,196 34
> 12/19/2005 07:02 PM 42,110 35
> 12/20/2005 06:34 PM 13,367 36
> 12/20/2005 06:43 PM 5,028 37
> 12/20/2005 06:50 PM 7,492 38
> 12/20/2005 07:18 PM 140,230,662 39*
> 12/20/2005 07:28 PM 467,101,582 40*
> 12/21/2005 02:45 PM 75,470 41
> 12/21/2005 02:50 PM 33,306,483 42*
> 12/21/2005 03:49 PM 97,284,571 43*
> 12/21/2005 03:58 PM 2,111 44
> 12/21/2005 07:03 PM 196,371 45
> 12/22/2005 05:35 PM 29,085 46
> 01/03/2006 11:19 AM 3,863 47
> 01/03/2006 11:30 AM 8,275 48
> 01/03/2006 11:32 AM 14,856 49
> 01/03/2006 12:39 PM 3,359 50
> 01/04/2006 04:13 PM 20,954,762 51
> 01/04/2006 04:16 PM 147,230 52
> 01/05/2006 05:36 PM 48,288 53
> 01/05/2006 05:43 PM 61,098 54
> 01/06/2006 12:40 PM 32,668,415 55
> 01/06/2006 02:43 PM 32,252 56
> 01/06/2006 02:44 PM 476,279 57
> -------------------------------------------
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.371 / Virus Database: 267.14.14/222 - Release
> Date: 05/01/2006
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.16/225 - Release Date: 09/01/2006
-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.16/225 - Release Date: 09/01/2006
 
-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.16/225 - Release Date: 09/01/2006
 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.16/225 - Release Date: 09/01/2006
-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.16/225 - Release Date: 09/01/2006
 
-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.14.19/231 - Release Date: 16/01/2006
 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org