On Thu, Apr 17, 2003 at 07:45:45AM -0500, cmpilato@collab.net wrote:
> Hm...makes me wonder if you don't actually have a bad checksum in your
> repository. :-)
>
> Try using Berkeley's db_dump and db_load tools to dump and load,
> respectively. That won't do any Subversion-ish error-checking.
Though google for 'subversion db_dump' turned up nothing of any value, I take
it I am supposed to run db_dump on each file in my repository, except a few,
though I can't see which ones. This worked for several of them, until 'strings', which complained loudly, even after running db_recover:
bash-2.05a$ /usr/local/BerkeleyDB.4.1/bin/db_recover -cv
db_recover: Finding last valid log LSN: file: 23 offset 6564
db_recover: Recovery starting from [23][28]
db_recover: Recovery complete at Thu Apr 17 09:53:55 2003
db_recover: Maximum transaction ID 8000058c Recovery checkpoint [23][6564]
db_recover: Recovery complete at Thu Apr 17 09:53:56 2003
db_recover: Maximum transaction id 80000000 Recovery checkpoint [23][6564]
bash-2.05a$ foo(){ /usr/local/BerkeleyDB.4.1/bin/db_dump -f bak/$1 $1; }
bash-2.05a$ foo strings
db_dump: page 8: illegal page type or format
db_dump: PANIC: Invalid argument
db_dump: fatal region error detected; run recovery
db_dump: fatal region error detected; run recovery
db_dump: fatal region error detected; run recovery
db_dump: fatal region error detected; run recovery
db_dump: DB->stat: DB_RUNRECOVERY: Fatal error, run database recovery
db_dump: fatal region error detected; run recovery
db_dump: close: DB_RUNRECOVERY: Fatal error, run database recovery
db_dump: fatal region error detected; run recovery
db_dump: dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 17 18:59:29 2003