On 3/12/07, Flavio Stanchina <email@example.com> 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.
Thanks for the advise. I will hold that in abeyance as a last resort.
But first I'd
like to see if I can recover or repair the repository (or at least
happened). I'm new to SVN, so please bear with me.
I noticed that the db dir in this repo has current.tmp, current.2.tmp,
current.3.tmp, all the way up to current.22.tmp, whereas other repos
(ones we can commit to) only have current. What are all these other
current.* files? Uncommitted transactions? I suspect their presence
is the cause of the problem.
As another data point, I also see that the files up to and including
current.11.tmp are older then current and have older revision
numbers in them, while current.12.tmp through current.22.tmp
are newer and have a higher revision number.
I tried running "svnadmin lstxn ..." on this repo - that returns:
I thought that would be a transaction number that I could pass to svnlook and/or
rmtxns. But when I try something like this:
svnlook -t '2453-1' changed ....
svnlook: Reference to non-existent node '0.0.t2453-1' in filesystem ...
What does this output from lstxn mean? How can I use it?
> Then you might want to check what's different between the broken repo and
> the fresh one.
> That 'H:' drive letter makes me suspect that you're storing the repo on a
> network drive. I would rather do version control with pencil and paper than
> keep a repo on a network drive. If that's actually what you're doing, set
> up a server instead.
Yes, this repo is on a network drive. I agree with you completely, but I did not
set this up, and I don't (at this point) have the power to change that
- I am at new
client and this is only my third day. Also, they are using a FSFS repo, which
from what I have read works on a network drive.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Mar 12 22:28:14 2007