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

Re: urgent: subversion repository does not react.

From: Lukas Ruf <ruf_at_rawip.org>
Date: 2004-08-04 21:59:44 CEST

> Lukas Ruf <ruf@rawip.org> [2004-08-04 20:55]:
>
> > Ben Collins-Sussman <sussman@collab.net> [2004-08-04 19:37]:
> >
> > On Wed, 2004-08-04 at 10:47, Lukas Ruf wrote:
> >
> > > db3_recover -cv -h PromethOS.damaged.20040804/db db_recover:
> > > DBENV->open: Invalid argument
> > >
> >
> > db3_recover isn't going to work on a db4 database. :-)
>
> ok, i see.
>
> >
> > > db4.2_recover -cv -h PromethOS.damaged.20040804/db db_recover:
> > > Finding last valid log LSN: file: 4107 offset 993287
> >
> > Did it report success? failure? Is it working?
> >
>
> that's how it finished.
>
> However, svnadmin still report the same problem.
>

I restored the repository from a backup taken yesterday night --
hence, lost the changes of people between 8 and 10am this morning :-(.

It seems that db4.2_recover eats my __db.??? files. At least after
running the db4.2_recover tool, they are not around anymore:

==>$ ls PromethOS/db/__db.00?
PromethOS/db/__db.001 PromethOS/db/__db.003 PromethOS/db/__db.005
PromethOS/db/__db.002 PromethOS/db/__db.004
==>$ svnadmin verify PromethOS
svn: Berkeley DB error while checkpointing after Berkeley DB transaction for filesystem PromethOS/db:
Invalid argument
==>$ ls PromethOS/db/__db.00?
PromethOS/db/__db.001 PromethOS/db/__db.003 PromethOS/db/__db.005
PromethOS/db/__db.002 PromethOS/db/__db.004
==>$ db4.2_verify -h PromethOS/db __db.004
db_verify: Page 0: pgno incorrectly set to 4294967295
db_verify: Page 0: bad magic number 4244635647
db_verify: Page 0: bad page size 0
db_verify: Page 1: partially zeroed page
db_verify: Page 2: partially zeroed page
db_verify: Page 3: partially zeroed page
db_verify: Page 4: partially zeroed page
db_verify: DB->verify: __db.004: DB_VERIFY_BAD: Database verification failed
==>$ db4.2_recover -cev -h PromethOS/db
db_recover: Finding last valid log LSN: file: 4107 offset 925313
db_recover: Recovery starting from [3071][28]
db_recover: Log sequence error: page LSN 4006 512107; previous LSN 4105 1047360
db_recover: Recovery function for LSN 4106 590 failed on forward pass
db_recover: PANIC: Invalid argument
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
==>$ ls PromethOS/db/__db.00?
ls: PromethOS/db/__db.00?: No such file or directory

Hence, I assume there is a problem with my db4.2 environment.

Am I mistaken?

wbr,
Lukas

-- 
Lukas Ruf           | Wanna know anything about raw |
<http://www.lpr.ch> | IP? -> <http://www.rawip.org> |
eMail Style Guide: <http://www.rawip.org/style.html>|
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 4 22:00:00 2004

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