Hello again!
I'm trying to get a working copy of the repository, but no luck so far.
When I run svnadmin recover on the backup I get the following error:
svn: DB_RUNRECOVERY: Fatal error, run database recovery
svn: bdb: Ignoring log file: /backup/svnppc/db/log.0000000026: magic number
0, not 40988
svn: bdb: Invalid log file: log.0000000026: Ogiltigt argument
svn: bdb: PANIC: Ogiltigt argument
svn: bdb: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
I've also tried making a hotcopy of the backup-repository to a new location
and using the --clean-logs switch but I get the same message.
Without the clean switch I get the following error message:
SIBMASTER:/backup # svnadmin hotcopy /backup/svn/oldfull/svnppc/
/backup/svnppctest/
svn: Ogiltigt argument
svn: bdb: Ignoring log file: /backup/svn/oldfull/svnppc/db/log.0000000026:
magic number 0, not 40988
svn: bdb: DB_ENV->log_put: 26: Ogiltigt argument
svn: bdb: Ignoring log file: /backup/svn/oldfull/svnppc/db/log.0000000026:
magic number 0, not 40988
svn: bdb: DB_ENV->log_put: 26: Ogiltigt argument
Any suggestions?
/ Peter
-----Original Message-----
From: Peter Hartlén [mailto:peter.hartlen@sib.se]
Sent: Wednesday, August 09, 2006 9:22 AM
To: users@subversion.tigris.org
Subject: New subversion version on new server?
Hi!
Our subversion server is seeing the end of it's life time, we recently got
some corrupt files in the database directory (bad blocks on some log-files)
and need to revert to a backup.
Instead of exchanging the drive we intend to buy a new server, and also
upgrade subversion from 1.1.3 r12730 (current version) to latest release.
Would there be any problems with copying the repositories from the old
machines backup to the new machine with the new version of SubVersion
(1.3.2)?
Regards,
Peter Hartlén
Received on Wed Aug 9 10:53:39 2006