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

Re: PLEASE Help with Repository CORRUPTION!

From: Stephane Clodic <sclodic_at_teaser.fr>
Date: 2005-03-24 20:29:18 CET

On Thu, Mar 24, 2005 at 11:40:59AM -0500, Robert S. Sfeir wrote:

Hello,

> Guys I've been trying my darndest to figure out what happened to the
> repository at revision 377 that is causing me to not be able to
> svnadmin dump the repository. Right now I get the same error that
> svnadmin verify gives me.

I meet this disagreement just yesterday and was unable to recover my
repository ; perhaps should I post to this list about this BerkeleyDB problem.

I started over with my working copy (I'm the only user of this repos)
with FSFS "backend".

> We are at revision 498 right now. The
> dump command stops like this:
>
>
> Node-path: mesquite/trunk/src/com/codepuccino/mesquite/service/
> Attribute.java
> Node-kind: file
> Node-action: add
> Prop-content-length: 10
> Segmentation fault

[snip]
> ANY clue would be great, and ANY suggestions on how I can properly
> rebuild the repo would be great too, even if it means losing a couple
> of revisions.

ok, let's start what I've tried yesterday but I'm not sure this suits your
problem.

First, backup your repository in a new location, this new one will be your
recovery-working repository.
You could use 'svnadmin hotcopy' for this.

Of course, I suppose I have tried all 'svnadmin verify $NEWREPOS' and
'svnadmin revocer $NEWREPOS' commands.

Then,
% cd $NEWREPOS/db/
% rm __log.* log.*
(I'm not sure about this, I read it in the FAQ ...)

You could try to use db_recover

% db_recover -v

In last ressort, I tried this :

for file in changes copies nodes representations revisions strings \
transactions uuids ;
do
   mv $file $file.old
   db_dump $file.old > $file.tmp
   db_load $file < $file.tmp
done

You could compare $file and $file.old which need to be the same size.

The file named "strings" contain all your repository.

In my case, with this method I was able to recover from revision 3 to
revision 48 but not to the last revision (55).

I'm not sure this help you a lot ... I'm looking for information for
Berkeley SVN repository recovery method.

Regards

-- 
Stephane Clodic
France Teaser
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 24 20:32:04 2005

This is an archived mail posted to the Subversion Users mailing list.