Michael & Mikaela Krueger wrote:
> Hi,
>
> I run a Linux server (SuSE 9.2) with Subversion that came with it...
> 1.2 something I would say.
> I have a server directory under:
> /srv/svn/repos/
> in which all of my repositories reside.
> Now one of my repositories (actually the most important one) seems to
> be broke.
> Most of the times when one of the repositories reports a berkley DB
> error in ViewCVS, a quick svnadmin recover <repository> does a quick
> job fixing any issues. This time it doesn't.
> Any SVN command, be it svnadmin, svn, svnlook that I execute on that
> repository will just hang. I'm not able to recover it. Does anyone
> have expirience with this? Anyone able to recommend a solution to
> recover the project?
Yes. Take it offline, back it up if possible, do a hot-copy.py backup as
well if possible, then update your SuSE to 10.0 and your Subversion to
1.3.1.
SuSE makes claims that they will support a release for 7 years, but *who
cared!!!*? The differences in kernel and database tools between 9.2 and 9.3
alone justify the upgrade, going to 10.0 should just sweeeten the deal. And
subversion 1.3.1 gets you a stack of useful new features.
Even better, after your OS and subversion is updated, switch the back-end
database from Berkeley DB to FSFS for better reliability. BDB was cool, but
it's overpowered for Subversion use, and very difficult to repair corrupted
databases. And the company that made it, Sleepycat, was recently purchased
by Oracle. I think we can expect Oracle to ruin it within 2 years the same
way they trashed the Stettor calendar server. Many open source tools have
moved away from BDB for various reasons: cross-platform use for Subversion
helped drive the use of FSFS as the new default database.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun May 7 01:49:25 2006