[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: strange BD issues on new repository

From: Jani Averbach <jaa_at_jaa.iki.fi>
Date: 2004-11-17 06:52:20 CET

On 2004-11-17 05:37+0000, maxvamp@comcast.net wrote:
> Hello,
> I have setup subversion 1.1 against a DB 4.3 setup. This is all
> done on OSX ( not using fink )

Berkeley 4.3 isn't a supported version with 1.1 at the moment. Downgrade your
version to the 4.2.52 and everything should be fine.

The support for 4.3 went in with r11871 @ trunk.

Br, Jani

> Everything seems to be OK, and I was even able to look at the
> empty repository through Apache on another machine. Being stupid,
> I tried to use a client ( svnX ) to create a directory off the
> repository root, and after that, I now get the following error
> when trying to do a svnadmin verify or any other general file
> checkout , checkin , etc on the repository :
> Berkeley DB error while fetching string length for filesystem
> /Volumes/RAID_5/Code_Vault/svn/db: DB_BUFFER_SMALL: User memory too
> small for return value
> svnadmin recover will operate without a hitch, but afterwards,
> everything is still screwed up.
> Anyone know why this happened, and more importantly... how to
> recover the repository? I have nothing in this repository worth
> saving, but I would really hate to have the same problem happen in
> the future and loose much valuable data.
> One last question....
> I read the section on backup... but as I am the only user of the
> repository, what are my chances of trashing my repository if I use
> a backup program ( such as Retrospect or BackupExec ) to backup my
> repository instead of using the python scripts.
> Thank you for all of your help...
> Hugh

Jani Averbach
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 17 06:53:04 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.