repository corrupted repeatedly
From: Will Glass-Husain <wglass_at_forio.com>
Date: 2005-09-28 21:27:17 CEST
I'm having trouble with a repeatedly corrupting repository. I've searched the mailing list and issues tracker haven't got any insights.
Setup: Linux (Suse 9.2) with Subversion 1.0.8, Apache 2.0.49, Berkeley DB 4.2. I haven't updated Subversion since I can't seem to find a later Suse RPM. (I may try compiling if I get desperate).
The problem. Three times in the past few days my (recently created) repository has become corrupted. Symptoms:
$ svn log
svn: Berkeley DB error while checkpointing after Berkeley DB transaction for filesystem /var/svn/src1/db: Invalid argument
... (2)No such file or directory: cannot access type map file: HTTP_UNAUTHORIZED.htm
The last time I had this issue I recovered the database, then changed the permissions to be readable by the apache2 user.
This worked. The next time this happened it failed:
$ cd /var/svn/src1/db
db_recover: Finding last valid log LSN: file: 68 offset 102818
Any tips for where I should investigate further? Or should I just grit my teeth and compile the latest subversion (scrapping the Suse RPM system).
This is an archived mail posted to the Subversion Users mailing list.