Markus Tacker wrote:
> Hoi Max,
>
> Max Bowsher wrote:
>> Odd. Very odd.
>>
>> Ensure nothing is trying to access the repository
>> $ db_recover -v -h /var/svn/repos/sms/db
>> $ svnlook youngest /var/svn/repos/sms
>
> That's interesting.
> I have no db_recover but
> - db4_recover
> - db4.1_recover
> - db4.2_recover
>
> # db4_recover -v -h /var/svn/repos/sms/db
> db_recover: Ignoring log file: /var/svn/repos/sms/db/log.0000000002:
> unsupported log version 7
> db_recover: Invalid log file: log.0000000002: Invalid argument
> db_recover: PANIC: Invalid argument
> *** glibc detected *** free(): invalid pointer: 0x0804b538 ***
> Aborted
>
> # db4.1_recover -v -h /var/svn/repos/sms/db
> db_recover: Finding last valid log LSN: file: 2 offset 186395
> db_recover: Recovery starting from [2][161035]
> db_recover: Recovery complete at Mon Apr 18 09:35:37 2005
> db_recover: Maximum transaction ID 80002819 Recovery checkpoint
> [2][186395]
> db_recover: Recovery complete at Mon Apr 18 09:35:37 2005
> db_recover: Maximum transaction id 80000000 Recovery checkpoint
> [2][186395]
>
> # db4.2_recover -v -h /var/svn/repos/sms/db
> db_recover: Ignoring log file: /var/svn/repos/sms/db/log.0000000002:
> unreadable log version 7
> db_recover: Finding last valid log LSN: file: 3 offset 0
>
>
> May it be that subversions uses the wrong version of db* programs to
> access
> the db?
Subversion does not use the db* programs, rather, it uses the db library
directly.
By the way, that sequence of commands will have upgraded the repository in
question from 4.1 to 4.2 format.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 18 11:14:56 2005