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

Re: Upgrading to 1.3.2: "svnadmin: File already exists"

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-08-17 17:54:48 CEST

On 8/17/06, Magnus Naeslund(k) <mag@kite.se> wrote:
> Ben Collins-Sussman wrote:
> >> When I was dumping and loading a repository (upgrading from 1.2.3 to
> >> 1.3.2) I got this nasty error message:
> >
> > Random side question: why were you dumping/loading? Changing from
> > BDB to FSFS or something?
> I always dump/reload to:
> 1) See that dump/reload works
> 2) Let subversion have an opportunity to optimize the repository

Optimize? Not sure what you mean there. If you dump an FSFS
repository and then reload it into a new FSFS repository, I'd expect
the two repositories to be byte-for-byte identical. It's not like
there's some sort of defragmentation going on. :-)

> I know that I didn't need to dump/reload for 1.3.x, but i do this as a routine.
> I was lucky I did this, otherwise a restore from the backup would have shown this error = really bad situation.

I'm not sure I understand the reasoning here. You might have
uncovered a bug in the code which creates a dumpfile; I doubt you've
uncovered a deep corruption within the structure of your repository.
Possible, but not as likely.

(Do you use 'svnadmin dump' as a backup? That's awfully slow. You
might just want to copy the repository.)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 17 18:10:09 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.