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

Re: 1.6.3: problems with svnadmin 'pack' and 'upgrade' on windows

From: Hyrum K. Wright <hyrum_at_hyrumwright.org>
Date: Thu, 30 Jul 2009 16:01:15 -0500

On Jul 30, 2009, at 3:50 PM, Ray Navarette wrote:

> Hi All,
>
> Hopefully, I’m doing something stupid and one of you can help me.
> If that’s not the case, then I have no idea what’s going on…
>
> I’ve recently upgraded our server from 1.4 to 1.6. I’d like to
> upgrade the repository to 1.6 also to take advantage of FSFS packing
> and merge tracking. So, as a sanity check, I wanted to first test
> out this upgrade. To do so, I did an ‘svnadmin hotcopy’ of the
> repository. This completed with what seems to be success (I can
> check out a working copy). I then attempt to upgrade with ‘svnadmin
> upgrade’ on the repo. This completes almost immediately with no
> text output to the console (is this expected?). It seems that the
> format file gets changed, but I’m surprised its this quick. Similar
> result with ‘svnadmin pack’, immediate completion and no output. I
> also expect there to be many less rev files (1 if my understanding
> is correct) after packing. There is still 1 file per revision.

If you are upgrading from 1.4, the repository won't be sharded, which
is a perquisite for FSFS packing. You'll need to shard the
repository, either by copying it using svnsync or using the (not-quite-
supported) fsfs-reshard.py script.

Once you've got a sharded 1.6 repository, packing it should then
consolidate all completed shards.

-Hyrum

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2377144

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-30 23:02:15 CEST

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.