Pejvan BEIGUI wrote:
> Max Bowsher wrote:
>
>>> What's to do next ?
>>
>>
>> That's very odd.
>>
>> Try the same thing, but "svnadmin dump" instead of "svnadmin verify".
>>
>> If you can get a complete dump, then just load it into a new repository,
and
>> problem solved.
>>
>> If not, post error messages.
>>
>
> Max!
> You're the Man, you saved my day :-)
>
> dumping and reloading back seems to have solved the problem.
> I've made a few checkouts, commits, updates, and everything seems to be
> working again.
>
> Any idea about what could have possibly gone wrong ?
Speculating:
I suppose it might be possible for Berkeley DB's files to become corrupted
in such a way that did not affect the data itself, but caused any attempt to
allocate more space within those databases to fail.
As to what might cause such subtle corruption - I have no idea.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 16 19:10:03 2004