McKenna, Simon (RGH) wrote:
>We still have over 2 dozen bdb repositories so I've written a NAnt
>script to perform this upgrade process ('tis part of a suite of NAnt
>scripts aiding Subversion administration when you have lots of repos)
>and it's working okay on test repos and hotcopies of production,
>however for the life of me I can't seem to get any output from:
>
>svnadmin list-unused-dblogs <repos-dir>
>
>I assume it's because there are no unused-dblogs to list :)
>
>
Yup.
>Paranoia warrants testing this before running on production, since
>hotcopies clean the logs right?
>
Yes.
> I've tried creating test repos with
>svnadmin --bdb-log-keep on v1.1.4 and then importing and adding,
>but I can't seem to make any dblogs unused. Any clues how?
>
>
--bdb-log-keep is right, but note that a) adding a fiew small files
won't fill a log file, and b) a log file doesn't "become" unused just
because its' filled up, a database checkpoint must happen first.
>Also, what are these "<repos-dir>\db\__db.00?" files we're deleting?
>
>
Those are BDB environment (shared-memory) files. Their format has
changed from 4.2 to 4.3, so they have to be removed during the upgrade.
Unfortunately, "svnadmin recover" won't do that for you (or rather,
it'll remove them, but then recreate them).
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 24 14:49:15 2005