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

Re: Macos X - corrupted repository ?

From: Achille Berès <achille_at_serverhouse.com>
Date: 2004-08-20 16:43:33 CEST

dump is not working.
I've upgraded to 1.1.0-rc2 and made another recover.

checkout is working, but not commit.
Full dump of the repos is still not working, but I've achieved to dump
all the commit made since last backup (one by one, incremental) and
load them ini a fresh copy of the repos from my backup.
So everything is back on track now

Thanks for your help.

On 20 août 04, at 07:27, Max Bowsher wrote:

> Achille Berès wrote:
>> HI all,
>> Using svn 1.06 on Mac OS 10.3 thanks to
>> http://homepage.mac.com/martinott/.
>> Looks like my repository has some problems.
>>
>> When I do : svn checkout file:////myrepo/trunk
>> localwp
>> Then answer is :
>> svn: Berkeley DB error while appending string for filesystem
>> file:////myrepo/trunk/db:
>> DB_RUNRECOVERY: Fatal error, run database recovery
>> Abort
>>
>> When I do: svn checkout file:////myrepo/ localwp
>> Then, Then answer is :
>> svn: Unable to open an ra_local session to URL
>> svn: Unable to open repository 'file:////myrepo'
>>
>> Bad news, recover doesn't seems to work :
>> svnadmin recover .
>> Please wait; recovering the repository may take some time...
>> Recovery completed.
>> The latest repos revision is XX.
>> But I still have the problem after ....
>>
>> Not everything is broken as "look" at the repos :
>> svnlook tree .
>> svnlook log .
>> does work…
>>
>> What can I do ?
>
> Try svn 1.1.0-rc2 - it gives more detailed errors in these
> circumstances.
>
> Does svnadmin dump work?
>
> Max.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 20 16:44:22 2004

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.