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

RE: Hotcopy failure

From: Kahn, Peter <pkahn_at_connected.com>
Date: 2005-09-27 17:46:38 CEST

Thanks, the response was timely and accurate. The problem was as you
and the docs described, but for a different reason. The docs mention a
problem when upgrading from one version of Berkeley to another. In both
cases I built Berkeley 4.3 from the same tar file. I recently upgraded
my hardware and OS. So, I moved from a system where I had built apache,
Berkeley and svn on RedHat 8.0 to one where I did so on Fedora Core 4.

The versions of the things I built didn't change. I used the same tar
files actually. What did change were the tools used to build them and
the underlying OS libraries. Apparently, this resulted in the same
symptom as upgrading the Berkeley library version. It seems logical
that this could cause a problem.

So, the cleanup of my unused db logs and the recovery action solved it.

-----Original Message-----
From: kfogel@newton.ch.collab.net [mailto:kfogel@newton.ch.collab.net]
On Behalf Of kfogel@collab.net
Sent: Monday, September 26, 2005 8:17 PM
To: Kahn, Peter
Cc: users@subversion.tigris.org
Subject: Re: Hotcopy failure

"Kahn, Peter" <pkahn@connected.com> writes:
> I have a repository on fedora core 4 with svn 1.2.1 and Berk 4.3.
> This db was created in the svn 0.6-0.7 time frame and hasn't been
> through a dump/load cycle since. I am using http and svnserve to
> access my repository. My repository I about 6.4 GB in size.
>
> For the past two days when I try to hotcopy my repository (even when I

> do not have any service accessing it) I get this error:
> svnadmin: DB_RUNRECOVERY: Fatal error, run database recovery
> svnadmin: bdb: Logging region out of memory; you may need to
increase
> its size
> svnadmin: bdb: Recovery function for LSN 18565 238216 failed
> svnadmin: bdb: PANIC: Cannot allocate memory
> svnadmin: bdb: PANIC: fatal region error detected; run recovery
>
>
> I am planning to do a dump/reload soon to allow me to go up to svn123,

> because I cannot without doing so for some reason. This being said,
> I'd like to be able to do this at my leisure. The fact that I cannot
> backup has my quite worried about the state of my db.
>
> When I run recover it finishes quickly and says there are no
errors....
> Could it be that my DB_CONFIG should be altered? I have 2GB of ram on

> the box, so I have no problem upping any values.
>
> Please let me know if anyone has any clues or suggestions. Thanks...

http://subversion.tigris.org/svn_1.2_releasenotes.html#bdb-upgrade
might have some useful information for you.

-Karl

--
www.collab.net  <>  CollabNet  |  Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 27 17:56:40 2005

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