Upgrading to 1.3.2: "svnadmin: File already exists"

Since this is a data-loss bug (in my view), I'm sending this to dev-list
aswell as the users-list. If I'm wrong in doing this, I apologize.

------------------------------------------------------------------------

When I was dumping and loading a repository (upgrading from 1.2.3 to
1.3.2) I got this nasty error message:

svnadmin: File already exists: filesystem 'repo1-restore1/db',
transaction '8684-1', path 'branches/someproject/v6.2/xproject/sl/docs/sl'
Command exited with non-zero status 1

The standard format dump file is about 7.9GB big, 1.7GB when dumped with
--deltas, the repo contains about 11000 revisions.
None of the dump files will load into a freshly created repo.

I don't see any problems with the paths, even if the sl/docs/sl looks
odd, that's the way it is.

So.. Does anyone know of this kind of problem?
So far I've only seen people converting from different other scm system
having this error. This repo is not converted.

 From the error message I would think that the dump is wrongly ordered
somehow, that the sl/docs/sl directory maybe was created, deleted and
the created again, and due to wrong ordering it gets created twice in a row.

I'll dig into the dump file soon, but I was just wondering if this is a
known bug.

Regards,
Magnus

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 16 13:52:29 2006