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

Re: problem with repository

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-05-17 21:41:15 CEST

Ramón wrote:

> here's a list of errors and the versions, don't know how the get the
> version of tsvn inside the repo and the working copy
>
> TortoiseSVN 1.3.3, Build 6219 - 32 Bit
> Subversion 1.3.1,
> apr 0.9.7
> apr-iconv 0.9.7
> apr-utils 0.9.7
> berkeley db 4.3.28
> neon 0.25.4
> OpenSSL 0.9.8a 11 Oct 2005
> zlib 1.2.3
>
> errors on working copy:
> commit:
> Error: Working copy 'D:\htdocs\ec' locked Error: Please execute the
> "Cleanup" command.
> cleanup:
> Subversion reported an error while doing a cleanup
> can't open directory 'd:\htdocs\ec\.....\.svn\tmp' system can't find
> that path

Ok, either create that folder inside the .svn folder yourself (just an
empty folder), or check out a fresh working copy.

> repo browser:
> error * can't read length line in file 'd:\svn\ec\db\revs\19'

That one's more serious: your repository is corrupt!

> export and checkout:
> Error: Can't read length line in file 'D:\svn\ec\db\revs\2'
> the first time i checked out the working copy was a long time ago and
> versions have changed but i've never had any problem, the las time i
> commited was about three weeks ago and maybe the client was updated to
> the current version since that time, don't have that info right now but
> i will ask to be sure!

Different versions would not corrupt a repository.

> i can see my repo is a little bit screwed, it is very important to me,
> is there a way to repair it or recover the data inside?

I hope you have a backup of your repository. Otherwise you might at
least loose *some* data as it looks now.

* get the Subversion command line client
* run 'svnadmin recover' on your repository
* if that doesn't help, try 'svnadmin dump path\to\repo > repodump.txt'
* you can then see in the file 'repodump.txt' what the repository
contained (of course, only if the repo isn't completely screwed).
* after that, create a new repository with 'svnadmin create
path\to\new\repo'
* then, run 'svnadmin load path\to\new\repos < repodump.txt'

I hope this helps. If not, you should ask on the Subversion mailing list
for help with your repository.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed May 17 21:41:35 2006

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