For what it's worth,
I've been using BDB from October 04, have upgraded SVN along the way, with
about 7 different repos. No problems till this 1.2.0 upgrade.
I've been working out an issue with a 4.54 GB Art repo in another tread,
migrating from SVN 1.1.4 to SVN 1.2.0, which for me was also a change from
BDB 4.2 to DBD 4.3
I followed the steps in the FAQ, and was unsuccessful in running longer the
15~25 revisions before crashing on me. The svnadmin recover did not work as
it usually would. I even tried *db_recover.exe -c -v* out of desperation,
but with no different result.
FAQ: After upgrading to Berkeley DB 4.3, I'm seeing repository errors.
When I tried to restore my backup, created during the FAQ, it caused
SVNADMIN to crash (around rev 200) when I tried restoring to a new BDB 4.3
I was successful in restoring my backup to FSFS ( total of 845 revisions )
I'll post back and let you know if I make it past revision 30 or so
revisions, which shouldn't take us that long to do.
And the size is now 3.18 GB (not sure if that has something to do with dump
and load from svnadmin or not)
Will I switch my other 6 repos, not if I don't have to, but stability means
everything, so I guess so unless there is a resolution I've overlooked or
has not been documented yet.
Christopher 'LanThief' Kreager
One of a 'Few Screws Loose, LC'
On 7/1/05, Mark Phippard <MarkP@softlanding.com> wrote:
> Dave Camp <email@example.com> wrote on 07/01/2005 02:49:57 PM:
> > I'd like to thank everyone for their input. It sounds like the
> > universal suggestion is to get off of bdb as soon as possible and
> > upgrade to fsfs.
> > Is there anything I need to look out for when migrating from svn/bdb
> > 1.1.2 to svn/fsfs 1.2 (other than following the instructions in the
> > release notes or whatever)?
> The main thing is to dump your repositories *before* you do your upgrade
> to 1.2. Just in case, your BDB version updates in the process. For
> example, if your BDB moves from 4.2 to 4.3 then your repositories will be
> inaccessible. Since you are on OS X, this probably would not happen
> without knowing it, but to be safe I would do this:
> svnadmin dump all repositories
> upgrade to 1.2
> svnadmin create all repositories
> svnadmin load all repositories
> This will also give you the performance gain you get from the XDelta
> algorithm used in 1.2.
> Scanned for SoftLanding Systems, Inc. by IBM Email Security Management
> Services powered by MessageLabs.
> To unsubscribe, e-mail: firstname.lastname@example.org
> For additional commands, e-mail: email@example.com
Received on Fri Jul 1 23:59:25 2005