[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: Magnus Naeslund(k) <mag_at_kite.se>
Date: 2006-08-23 17:22:45 CEST

Ben Collins-Sussman wrote:
> 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. :-)

Well one example would if subversion would change delta algoritm.
But this part of the discussion is not important.

>> 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.

Well I'm not sure, but I like to verify that dump/restore works when I upgrade to another svn version.
Maybe you see that as silly, but I'm glad I tried it, as I found an actual problem (whatever reason for it).

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

Yes I use that format because I thought it was the most flexible format.
This might not be optimal as our repository grows, but I'll examine that later.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 23 17:25:44 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.