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

Re: SVN Dump Question

From: Andrey Repin <anrdaemon_at_freemail.ru>
Date: Thu, 18 Feb 2010 03:02:39 +0300

Greetings, Justin Connell!

> The reason, I'm asking such strange questions is that I have a very
> abnormal situation on my hands here. I previously took a full dump of
> the repo (for the reason you implied) where the original size of the
> repo on disk was 150 GB, and the resulting dump file ended up at 46 GB.
> This was quite unexpected (the dump is usually larger than the repos on
> smaller repos that I have worked on).

Sounds odd.
Have you tried running cleanup procedures? If you're using autoversioning
through some strange and unnatural (to Subversion) tools, this could
potentially cause lots of stalled transactions that lying under the hood,
wasting space, but not impacting the repository in any sensible way.

> Just as a sanity check, this is what I was trying to accompliesh:

> Scenario - The repo needs to get trimmed down from 150 GB to a more
> maintainable size. We have a collection of users who access the
> repository as a document revision control system. Many files have been
> added and deleted over the past 2 years and all these transactions have
> caused such an astronomical growth in the physical size of the repo. My
> mission is to solve this issue preferably using subversion best
> practices. There are certain locations in the repo that do not have to
> retain version history and others that must retain their version history.

> Proposed solution -

> 1. Take a full dump of the repo
> 2. run a svnadmin dumpfilter including the paths that need to have
> version history preserved into a single filtered.dump file
> 3. export the top revision of the files that do not require version
> history to be preserved
> 4. create a new repo and load the filtered repo
> 5. import the content form the svn export to complete the process

> Is this a sane approach to solving the problem? and what about the size
> difference between the dump file and the original repo - am I loosing
> revisions (the dump shows all revision numbers being written to the dump
> file and this looks correct).

> Another aspect could also be that there are unused log files occupying
> disk space (we are not using Berkley DB though) is this a valid
> assumption to make when using the FS configuration.

> Thanks so much to all who have responded to this mail, and all of you
> who take the time and read these messages

What you describing sounds... fair.
But first, I would suggest some steps that involve more, say, native
operations on repository.
Cleanup, hotcopy... See how would they affect it, and what would be the

 Andrey Repin (anrdaemon_at_freemail.ru) 18.02.2010, <2:56>
Sorry for my terrible english...
Received on 2010-02-18 01:05:40 CET

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.