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

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 19:51:14 CET

Hi,

Somehow I manged to kill my repository using TortoiseSVN. So switching
back to the command line client, trying to do a

        svn list $SVN

with $SVN being set to my file based repository path (file:///svn/)
shows me that there is nothing in the repository. Even though there are
three folders under $SVN.

The repository is a fsfs type repository, my clients under Linux and
cygwin are version 1.2.3. Linux accesses the repository via a NFS mount
and cygwin through a windows network mapping.

Now I found out that in the repository under the db folder the file
current is corrupted. Some weired text like "<xml ?". I had a month old
backup from the repository and there are two numbers and a letter (63 36
n). Now just out of curiosity I added those numbers and I was able to
list the repository again. However only two from the three folders. The
third folder got added after that backup. So my assumption is, I set the
repository to the version as of the backup?

Can anybody help me how to figure out what to write into the current
file in order to fix the repository and bring it to the current state?

I have three of the two folders checked out and in sync with the
repository. The third folder has changes that I wanted to commit.
Nothing big, so I could revert and bring it to the state of the
repository as well. Can I look through the checked out folders and
figure out what to put into the current file?

Thanks for any help.

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 21:02:49 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.