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

Re: db broken, recover and dump fails

From: Max Bowsher <maxb_at_ukf.net>
Date: 2005-05-09 16:45:51 CEST

Henrik Frisk wrote:
> Hi,
> After a power failure (I think that's what caused the problems to begin
> with) my repository got corrupt. I can do recover and check out files but
> I
> cannot commit. I have searched for info and I have tried many different
> methods. After doing a recovery, I can't even do a dump; It stops at
> revision 2, takes for ever, and than prints a million lines such as:
> svn: bdb: DB_ENV->log_flush: LSN of 118/920926 past current end-of-log of
> 1/2750
> svn: bdb: Database environment corrupt; the wrong log files may have been
> removed or incompatible database files imported from another environment.
> What I have been going through seems similar to what Dean Iverson
> described
> in this post:
> http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=30379, but
> I
> can't seem to find any replies.
> I have tried removing log and __db files and doing db_recover but nothing
> helps. Recovery exits normally but the problems remain (unable to commit -
> repository broken after I try).

cd path/to/my_old_repository
cd ..
svnadmin create --fs-type=bdb a_new_repository
cd a_new_repository/db
rm *s __db.* log.*
cd ../../my_old_repository/db
for i in *s; do
  db_dump -r "$i" | db_load -h ../../a_new_repository/db "$i"
cd ../..
svnadmin recover a_new_repository
svnadmin verify a_new_repository

If that doesn't work, tarball your old repository and put it somewhere I can
examine it.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 9 17:23:36 2005

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.