RE: SVN 1.8.1 Errors - Show Log and Commit New Files - SOLVED (FOR ME)
From: Geoff Field <Geoff_Field_at_aapl.com.au>
Date: Mon, 19 Aug 2013 09:19:01 +1000
Get your legacy material off BDB and onto FSFS, ASAP. At least make sure you have *good* backups and are prepared to lose all that data if you don't. BDB has been, in my experience with much older versions of Subversion and with years of Linux application experience, prone to data corruption from unpredictable and unrecoverable userland events and even the slightest blip of the OS or hardware layer. It has also repeatedly proven impossible to upgrade existing data sets to new BDB releases in place. Subversion fortunately has a workable backup system to provide data transfers: I've seen BDB systems that did not.
The servers are backed up nightly using IBM's Tivoli Storage Manager. I've had to recover repositories a few times using that tool, so I know it works for us.
BDB has never been my friend.
We've had a few corrupt repositories over the years. We got to the stage where we wrote an internal Wiki page on fixing corrupt repositories.
We had a colleague write an application to help with management of the repos. Unfortunately, he chose to create them in BDB format. That's why we have so many BDB repositories. Rather than recreate the build environment and rebuild the management application, I've edited the EXE file to replace the (DBCS) string that sets the format with spaces.
It seems I spoke too soon. It turns out that the updated SVN server 1.6.9 works for those few of our repositories that are in FSFS format. Unfortunately, our legacy repositories are almost all in BDB format and I'm loathe to touch them if I can avoid it.
Building SVN from source is not really a useful option, but we can do it (with a struggle) if we absolutely have to. Frankly, I'd rather convert all the repositories (and there are 100 all up, although some are in FSFS format already) than build the server code. Has anybody built a version that handles BDB in a DAV module?
> I have not deleted the Apache 2.0/SVN server 1.2.3
We can swap back to the other version fairly easily if we have to, just by stopping Apache2.2 and starting Apache2 (or vice-versa).
- The contents of this email, and any attachments, are strictly private
This is an archived mail posted to the Subversion Users mailing list.