RE: help recover svn repository

Thank u Andrey for your suggestion and for your honest answer

I already did all of your suggestion and its really does not work

I will try use some Berkley db_tool in order to restore the data

Thanks:)

-----Original Message-----
From: Andrey Repin [mailto:anrdaemon_at_freemail.ru]
Sent: Monday, April 06, 2009 4:07 AM
To: Odelia Polak; Odelia Polak
Subject: Re: help recover svn repository

Greetings, Odelia Polak!

>>> I would really appreciated if u could help me on the next error
>
>>> svn: Berkeley DB error while checkpointing after Berkeley DB
>> transaction
>>> for filesystem old_bdb/db:
>
>>> Invalid argument
>
>>> The following happened like that
>
>>> First the backup was running when the svnservice run
>
>>> Second the svn server crushed
>
>>> Third we tried to restore the data from tape
>
>>> Then I recover and discover that we have number of revisions and
when
>> I
>>> dump the file I get the next error
>
>>> Could u please help me
>
>> If only I can understand what you trying to say...
>> Your problem was (is) as follow:
>> 1. You have SVN server running
>> 2. You start backup process without locking the SVN database
>> 3. SVN server crashed, supposedly at the write operation to the file
>> being
>> copied for backup, thus locked at filesystem level.
>> 4. You tried to restore from a tape backup (by the way, from which
date?
>> From
>> date of crash or from previous date?)
>> 5. ???
>> 6. No profit
>
>> Am I right?
>> Without the errors text, I can't tell you much. Please post them.
>> And please disable HTML messages format.

> The steps are:

> 1. the svn server crushed and fail to restore the data base/
> 2. I restore the repository from the backup tape and get source
> week before crush
> 3. when I try to run recover I get
> "svn: Berkeley DB error while checkpointing after Berkeley DB
> transaction
> for filesystem old_bdb/db"
> 4. please Help me :)

Berkley DB... what is your SVN server version?

Try the following:
1. Shutdown SVN server
2. Rename your existing repository folder to something different.
3. Restore your repository fresh from backup.
4. Try 'svnadmin dump' your repository.
5. Pray it could be able to dump it to some point...

But... want a honest answer? I do not believe your quest could end in a
success... Here's why: You were copying repository without a lock, thus
while
you copying one part of it, the server was able to write in another
part,
altering the structure before, or, worse, after the point which you're
copying.
Thus, your copied data was already corrupted...

--
WBR,
 Andrey Repin (anrdaemon_at_freemail.ru) 06.04.2009, <4:55>
Sorry for my terrible english...
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1558164
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].