Simon Kennedy wrote:
> Max Bowsher wrote:
>> Simon Kennedy wrote:
>>
>> That "magic number" line is indicative of a malformed log file.
>>
>> First: MAKE A TARBALL/ZIPFILE BACKUP of the repository.
>>
>> Then, cd to the "db" subdir of your repository.
>> Delete __db.* and the logfile mentioned in the error.
>> Try to run "db_recover -cv" - if that succeeds (doesn't report errors),
>> try
>> "svnlook youngest" (a trivial test of repository access) - and if that
>> works, "svnadmin dump" your repository and reload into a newly created
>> repository.
>>
>> If not, redo these instructions, deleting all __db.* and all log.* files.
>>
>> You are on Windows, so you probably don't have the db_recover tool
>> already installed.
>> Get it from:
>>
>> http://subversion.tigris.org/files/documents/15/8848/db-4.2.52-win32.zip
>>
>> Max.
>>
>
> Thanks Max,
>
> I downloaded the db tools and the db_recover ran successfully.
>
> Is the reload from a dump necessary?
If you deleted all log.* files, yes. If not, its probably ok not to.
> This process takes a long time and
> it is quicker to simply copy over a backup and apply the recent commits
> (we record a dump of each commit with the post-commit script)?
>
> I was wondering why this type of corruption happens each time we have
> a power outage (we have had several in the last month). Is this
> specifically related to Windows NT? Would we better off under XP
> as we have planned to do this and maybe we should make the move sooner?
Eek! You certainly shouldn't be seeing corruption with anything like that
degree of predicatability.
It might be worth summarizing that information to the dev@ list, to get more
attention.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 29 13:10:13 2004