Thanks for the suggestion Paul.
I was able to verify that the md5sum values change for a repository revision
file when the
repository is showing the checksum errors. So it indeed looks to be a
hardware / system
problem.
Scott
----- Original Message -----
From: "Paul Koning" <pkoning@equallogic.com>
To: <scott.harger@pinpointinsight.com>
Cc: <users@subversion.tigris.org>
Sent: Wednesday, October 26, 2005 3:57 PM
Subject: Re: checksum problem
>>>>>> "Scott" == Scott Harger <scott.harger@pinpointinsight.com> writes:
>
> Scott> We recently converted from CVS to Subversion and are having
> Scott> intermittent problems with our repository. We'd appreciate any
> Scott> suggestions help us resolve them. ...
>
> Scott> To eliminate bdb as a cause of our problems, we created a fsfs
> Scott> backed repository and loaded it with a dump of the latest
> Scott> revision from the bdb repository (a dump created during one of
> Scott> those times that it could run successfully without the
> Scott> checksum errors)
>
> Scott> Sadly we are still seeing the weird behavior with the fsfs
> Scott> backed repository in that we cannot check out certain
> Scott> directories at certain times. ...
>
> My guess is a data integrity problem on your system -- disks, bus,
> memory, ...
>
> You could do md5sum on the repository files (the internal guts of the
> repository) while it is having the problem, and again when it seems to
> magically correct itself. I'd expect a mismatch somewhere.
>
> paul
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 27 06:30:47 2005