Ya, I will definitely load the repo into fsfs on the new system.
I tried the recovery to no avail yesterday.
I just completed a restore of the VM to a state before all this started and
here is what I now see.
Trying to run an svnadmin dump gives me:
svn: bdb: Program version 4.2 doesn't match environment version
When I look at the versions using ldd, here is what I see:
mod_dav_svn (which is what everyone is using to check in) is linked to
svnadmin is linked to libdb4.2
svn is linked to libdb4.2
So is my solution to fix this to upgrade svnadmin to a version linked to
On Fri, Aug 16, 2013 at 12:40 PM, Chris Shelton <cshelton_at_shelton-family.net
> This page of the subversion book sounds like it might be helpful in your
> I am sure that switching to a FSFS repository data store with your new
> system is advisable.
> On Fri, Aug 16, 2013 at 1:37 PM, Dana Epp <dana_at_vulscan.com> wrote:
>> I have inherited a REALLY old SVN server that was mismanaged for years.
>> They were using WebDAV successfully for so long they never noticed any
>> issues under the hood, but the BDB is corrupt and cannot run an svnadmin
>> dump on it to move it to a new server that I built that has all the latest
>> SVN bits.
>> The old system is running SVN 1.1.1 with BDB 4.2.52.
>> At this point after following several different pieces of guidance online
>> the system starts a dump, and ends up after several "Dumped revision #"
>> pukes out hundreds of the following lines:
>> svn: bdb: DB_ENV->log_flush: LSN of 56874/862249 past current end-of-log
>> of 1/2786
>> svn: bdb: Database environment corrupt; the wrong log files may have been
>> removed or incompatible database files imported from another environment
>> Does anyone know where I should go from here? Does anyone know of anyone
>> consulting on these sort of repairs? I did a full export of the whole repro
>> using WebDAV before I started this, so I have HEAD, but I don't want to
>> lose the history if I don't have to.
Microsoft Security MVP
Received on 2013-08-17 01:15:26 CEST