Ryan Schmidt wrote:
> On Oct 4, 2007, at 16:56, Rush Manbert wrote:
>
>> I needed to make a "sanitized" version of my repository by getting
>> rid of source files and all of the history. I did the following:
>> 1) Used svnadmin hotcopy to copy the repo
>> 2) Did a checkout from the copy
>> 3) Deleted everything that's sensitive in the WC
>> 4) Did svn commit back into the copy. The commit created revision 578.
>> 5) Did svnadmin dump /path/to/copy --revision 578 >dumpFile
>> 6) Did cat dumpFile | svnadmin load /path/to/sanitized/repo
>>
>> My original repository size is 560.6 MB.
>> My copy repository size is 560.7 MB.
>> My sanitized repository (created by svnadmin load) size is 3.19 GB.
>>
>> I am wondering why the sanitized repository is so large.
>>
>> I am using svn 1.4.3 under Mac OS X 10.4.10. The back end is FSFS.
>>
>> I can run svnadmin verify successfully on the sanitized repository.
>> It displays:
>> * Verified revision 0.
>> * Verified revision 1.
>>
>> I didn't find anything pertinent searching in Google. Does anyone
>> have any idea why this would happen, and/or how I can get the
>> sanitized repository back down to a reasonable size?
>
>
> If you have branches and/or tags or have other elements in your
> repository that were copied from other elements in your repository, in
> your old repository these were represented as cheap copies. Now, they
> are represented as expensive complete copies, because you have
> discarded the history during which the copy occurred.
>
> You may instead want to try svnadmin dump, then svndumpfilter to remove
> bits, then svnadmin load. This would retain the history.
>
Oh, I certainly have now-not-cheap copies in the repository. Bummer. But
understandable.
I will check out svndumpfilter.
Thank you for the help.
Best regards,
Rush
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 5 01:27:46 2007