eg wrote:
> Thomas Hemmer wrote:
>> Thanks for the pointer!
>>
>> In the meantime, I managed to get things running again.
>>
>> I took the approach to replace the stored MD5 hash by the expected
>> one; although I can't tell for sure whether the affected file is
>> *really* consistent now (since it is some strange binary format) I am
>> happy to have my repository back in a usable state.
>
> What happens when you run "svnadmin verify REPOS_PATH" (server side)?
>
> That should tell you whether the repository revisions are all ok.
>
>>
>> But I would be even happier if I had any clue about the reason of the
>> misbehaviour...
>
> Understood.
>
> If you do happen to find out (e.g. hardware issues), it would be good to
> hear on the list.
I suspect v1.4.5 since after upgrading (thru svnadmin dump)
my server from v1.4.3 I started getting a lots of MD5 problems.
After upgrading to v1.4.6 I have had none (knock on wood)
-pekka-
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-05 22:30:35 CET