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

Re: Help! How can I fix the $SVN/db/current file. My fsfs repository got corrupted.

From: GŁnter Dannoritzer <dannoritzer_at_web.de>
Date: 2005-11-10 22:26:57 CET

Gale, David wrote:
>
> At a quick glance, the first number is clearly the HEAD revision. Try
> doing an 'svn info' of the working copies you have, and put the revision
> number reported by that in the first slot. I don't know what the other
> two items in the file are; glancing at several repositories, I can't see
> a pattern. One has '1rO o'; another has '5 1'. <shrug> Hopefully
> someone else knows how to find what goes there, if setting the HEAD
> revision number isn't enough...
>
> Good luck!
> -David
>

Thanks David, that help me a step further. I found out that 72 is the
latest revision number. I wrote that into the current file and did a
svnadmin dump of the repository. It showed me that it would dump all the
revisions up to 71. For 72 it reported an error in the file:

 /svn/db/revprops/72

So I looked into that file and it is in binary form. The other files of
lower revision all seem to be in text form.

I am thinking now whether I should just dump revision 72 and revert the
repository to revision 71. I haven't added too much recently, so I could
probably live with that loss. The other idea I have is to just commit
the changes from the checked out version that reported me that top of
revision is 72.

Guenter

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 10 22:29:44 2005

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.