Complife wrote:
> In dealing with other errors, I deleted log files from the database. (Not
> realizing they had active data in them, (jeez they're called log files
> aren't they?)
Blowing away the transaction log files for any transaction controlled system
is seldom a good idea :-/
> I've finally got subversion and bdb talking but the bdb seems to be having
> problems. I do one commit and it seems happy. Then after that I get error
> messages about unsupported log versions.
>
>
> I tried running recover but got the following:
>
> home/svn # db4_recover -h /home/svn/db
> db_recover: unable to join the environment
> db_recover: Ignoring log file: /home/svn/db/log.0000000001: unsupported
> log
> version 8
> db_recover: Invalid log file: log.0000000001: Invalid argument
> db_recover: PANIC: Invalid argument
>
> killing it was the only way out. Now it appears that things are working
> again !?!
>
> Trying to dump the repository gives
> svnadmin dump /home/svn >dump.txt
> svnadmin: Berkeley DB error for filesystem /home/svn/db while
> checkpointing
> after Berkeley DB transaction:
> Invalid argument
> svnadmin: bdb: DB_ENV->log_flush: LSN of 3614/1047201 past current
> end-of-log of 1/365735
> svnadmin: bdb: Database environment corrupt; the wrong log files may have
> been removed or incompatible database files imported from another
> environment svnadmin: bdb: changes: unable to flush page: 0
> svnadmin: bdb: txn_checkpoint: failed to flush the buffer cache Invalid
> argument
OK, that situation is pretty much normal having trashed the existant
logfiles.
!!! MAKE A BACKUP !!! and then try this recipe:
cd /home/svn/db
rm log.* __db.*
for i in *s; do mv ${i} ${i}-old && db4_dump ${i}-old | db4_load ${i}; done
svnadmin recover ..
svnadmin verify ..
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 7 23:22:27 2005