You may be better off just upgrading to fsfs rather than berkely also...
As long as your old repository is 'healthy', you can just pipe it into
your new fsfs repository, update your svnserve and/or apache conf, and
all should be fine.
We had lots of db corruptions in many versions of svn, and since moving
to fsfs, have had no problems.
cheers
Rach
Branko ÄŒibej wrote:
> Reuben Sivan wrote:
>
>> Hi,
>>
>> Since I updated to svn 1.2.1, I started getting errors such as:
>>
>>
>>
>>> svnlook info svndb
>>>
>>
>>
>> svn: Berkeley DB error while checkpointing after Berkeley DB
>> transaction for
>> filesystem svndb/db:
>> Invalid argument
>> svn: bdb: DB_ENV->log_flush: LSN of 388/370139 past current
>> end-of-log of
>> 1/11170
>> svn: bdb: Database environment corrupt; the wrong log files may have
>> been
>> removed or incompatible database files imported from another environment
>> svn: bdb: strings: unable to flush page: 0
>> svn: bdb: txn_checkpoint: failed to flush the buffer cache Invalid
>> argument
>>
>>
>> Running svnadmin recover brings it back to functional, but not for
>> long, a
>> while later I get the above again, and again I need to run svnadmin
>> recover.
>>
>> All help will be greatly appreciated.
>>
>>
> You did read the bit in the readme about upgrading from 1.1.x to 1.2.x?
>
> It's also here: http://subversion.tigris.org/faq.html#bdb43-upgrade
>
> -- Brane
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 17 15:19:34 2005