Karl Fogel wrote:
>
> Blair Zajac <blair@orcaware.com> writes:
> > This looks like fun:
> >
> > Was trying a commit which hung, and trying to recover the database fails:
> >
> > svnadmin recover test
> > Acquiring exclusive lock on repository db.
> > Recovery is running, please stand by...
> > Recovery completed.
> > subversion/libsvn_fs/bdb/bdb-err.c:61: (apr_err=160029)
> > svn: Berkeley DB error
> > svn: Berkeley DB error while opening `changes' table for filesystem test/db:
> > Invalid argument
> >
> > Any ideas?
>
> Whoa. No -- not even any reason to think this is the same problem as
> the ones we're experiencing with svn.collab.net right now, really.
>
> What version of server? Of Apache? What OS? What exact version of
> Berkeley? Was the database created with the same Berkeley that you
> later ran db_dump with? That error you saw
OK, here you go.
RedHat 9 with all patches.
Apache/2.0.46-dev (Unix) mod_ssl/2.0.46-dev OpenSSL/0.9.7a DAV/2 SVN/0.20.1+
svn rev 5592
apr/apr-util/httpd from CVS on 2003-04-08.
Berkeley DB 4.1.25.
Yes, the same binaries and libraries are used.
> > $ /opt/i386-linux/db-4.1/bin/db_dump changes > z
> > $ /opt/i386-linux/db-4.1/bin/db_load changes.1 < z
> > db_load: Length improper for fixed length record 4087
> > db_load: Invalid argument
>
> ...is quite disturbing :-). Can you examine `z' and identify the bad
> record?
Hmmm, how do I do that?
Best,
Blair
--
Blair Zajac <blair@orcaware.com>
Plots of your system's performance - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 11 21:49:13 2003