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

Re: Can't commit because current already exists

From: Larry Martell <larry.martell_at_gmail.com>
Date: 2007-03-13 01:03:55 CET

On 3/12/07, Flavio Stanchina <flavio@stanchina.net> wrote:
> Larry Martell wrote:
> > We have a SVN repository on windows. Starting today, no one can commit.
> > Attempts to commit fail with:
> >
> > Error Commit failed
> > Can't move 'H:\path\to\svn\repo\db\current.21.tmp' to
> > 'H:\path\to\svn\repo\db\current':
> > Cannot create a file when that file already exists.
> > [...]
> > Right now I need to know how I can clean this up so developers can
> > commit again?
> > (And once that crisis is passed, I'd like to know how this happened.)
> Dump the repository, move away the original and load the dump in a fresh
> repo. Hopefully that should fix the problems.

No joy :-(

I dumped the repo, and that ran successfully - it dumped up to revision 3480,
which was the highest revision before this commit problem surfaced.

I then tried to load the dump into a freshly created repo. This ran up to rev
1102, then it failed with:

<<< Started new transaction, based on original revision 1103
     * editing path : Dynamic View.xml ... done.
svnadmin: Can't move
to '/cygdrive/h/Engineering/EA/SubversionRepositoryRestored/db/current':
File exists

However when I look in the SubversionRepositoryRestored/db dir there is not a
file called current.

Anyone know what I can do to repair this repository??


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 13 01:04:22 2007

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.