On Mar 6, 2007, at 13:35, Jared Hardy wrote:
> That sounds a little too dangerous. The way FSFS works makes it
> possible that the "oldest" revision files can hold necessary pieces of
> "newest" files. I think the semi-officially supported route is moving
> old revisions to different (larger, slower) volumes, including over
> NFS, and then soft-linking ("ln -s ..." in UNIX) them from their
> original position in the FSFS tree. Shut down and svn or Apache server
> access while you're doing this, just to be safe. Also be careful to
> keep the ACLs the same on the new volume.
Yeah, that should work.
> There is also an "svnobliterate.py" script in the contrib area
> somewhere, but I'm not that familiar with its proper use, so details
> will have to come from elsewhere. Otherwise, you will have to
> "svnadmin dump ..." to another larger volume, and get really familiar
> with the use of svndumpfilter. Loading a dump file into a 1.4.x FSFS
> repository, from an older version, will also cut the space used in
> about half, in my experience.
I thought "svnobliterate" / "svnadmin obliterate" was a concept that
had been proposed but that nothing had been implemented yet.
If you want to throw away the history of the first, say, 1000
revisions, you should be able to use "svnadmin dump" to dump
revisions 1001 thru HEAD, then move your repository out of the way,
then create a new repo, then load in the dumpfile. However, I believe
this will renumber your revisions, so all existing working copies
will become unusable and you will need to throw them away and check
out new working copies. Also, if the files that were in the first
1000 revisions are still around in the repository today, then getting
rid of the first 1000 revisions may not help you save any space. You
could try it out as a test -- just dump recent revisions, load them
into a new repository, and see if it's any smaller.
To reply to the mailing list, please use your mailer's Reply To All
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Mar 7 04:37:00 2007