Segfault after hot backup.

[Luke Quinane <lu...@octerbar.net>]

Hi,

I am currently having some problems using the hot-backup.py script.
Sometimes after I create a backup of my svn repository using the script
it is corrupt and causes both svnlook and svnadmin to segfault.

To reproduce the error I have made a new repository (attached) and added
a file. Using the backup script produced a working backup. I added a new
file, committed and ran the script again, however this second backup is
corrupt.

I am using svn 0.26.0 (r6550) and the hot-backup.py script from r6774. I
have BerkeleyDB version 4.1.25 install on my box (for db_recover and
db_archive), I also edited the two lines in the script to reflect this.

In the attached tar file "abd/bak/test-1" is the working backup,
"abd/bak/test-2" is the corrupt backup. "abd/test" is the original
repository, "abd/work/test" is a checked out version.


Thanks in advance,


Luke

Re: Segfault after hot backup.

[cm...@collab.net]

Luke Quinane <lu...@octerbar.net> writes:

> I am using svn 0.26.0 (r6550) and the hot-backup.py script from r6774. I
> have BerkeleyDB version 4.1.25 install on my box (for db_recover and
> db_archive), I also edited the two lines in the script to reflect
> this.

Is your Subversion linked against BerkeleyDB 4.1.25?  Please tell me
that you are using the same version of the Berkeley tools (db_recover
and db_archive) as the version against which your Subversion is
linked.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org