Need assistance with repairing repository corruption caused by known bug

[Ken Valentine <ke...@escription.com>]

Hello,

Any assistance you can provide would be greatly appreciated.  The
subversion setup I have is as follows

 

RedHat AS v3 , kernel 2.4.21-27.0.2.ELsmp
subversion-1.1.3-0.1.1.el3.rf

db4-4.1.25-8

 

As is well known, occasionally the repository becomes wedged, and
generally the "svnadmin recover" has been successful in restoring the
repository to a usable state for us.  Today however we hit this error:

 

svn: bdb: call implies an access method which is inconsistent with
previous calls

 

so I followed the instruction here:

 

http://subversion.tigris.org/faq.html#bdb41-tabletype-bug

 

but the same error occured during the svnadmin dump command.  The copies
table didn't actually appear to be corrupted; its dump file had
type=btree and no re_len= line, so I suppose that's why I got the same
error.  It *appears* that the changes table was corrupt, as it did have
type=recno and len=36, or something like that.  I tried performing the
suggested changes, but hit this error:

 

db_load: Lock table is out of available locks

db_load: Cannot allocate memory

 

As I say, any assistance you can give would be hugely appreciated.  My
experience with subversion or even Berkeley DB is, as you might guess,
not extensive.  

 

Thanks,

 

Ken


------------------------------
Kenneth Valentine
Escription, Systems Administration
(781) 455 - 8900  x210

 


eScription, The Leader in Computer Aided Medical Transcription