Brice Dardel escribio:
> The svn server is running what I think is the most up to date version:
> Berkeley db 4.2.52 from the default win32 setup package, upgraded
> from svn
> 1.0.2 last weekend (the repository is not accessible from outside the
> 5 people team so the step to 1.0.3 wasn't critical) and Apache
> 2.0.49. I heard some previous versions of BDB had issues with
> multiple cpus. I don't know if it's entirely fixed, or if windows fs
> is buggy (duh) under these conditions for the strict requirements of
You may try db_recover.exe. It's almost the same as 'svnadmin recover'
but it can give some more output.
You'll find it in the download page of the Subversion site as bdb tools.
> If other people start to report problems using svn on multiple cpus
> w2k machines, then there is a pattern. Without that... hard to tell.
I got a broken database some days ago. I forgot to tell the list that
we have Apache/Subversion running in a dual cpu box, failing to realize
that it may matter. Follows the output of db_recover:
db_recover: DB_ENV->log_flush: LSN of 112/193694 past current end-of-log of
db_recover: Database environment corrupt; the wrong log files may have been
ved or incompatible database files imported from another environment
db_recover: strings: unable to flush page: 0
db_recover: txn_checkpoint: failed to flush the buffer cache Invalid
db_recover: PANIC: Invalid argument
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
There were *no* manually removed logs nor incompatible imports. We *did*
an energy blackout, though.
Environment: Windows 2000 professional, Apache 2.0.48, Subversion 1.0.1
(berkeley db 4.2.52), dual cpu box.
After the blackout every commit hang. Same thing with 'svnadmin verify'.
Este mensaje ha sido analizado y protegido por la tecnologia antivirus www.trendmicro.es
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue May 25 11:11:44 2004