RE: Have an old SVN 1.1 DB corruption issue and need some help
From: Bert Huijben <bert_at_qqmail.nl>
Date: Sat, 17 Aug 2013 01:25:58 +0200
If all commits were through that mod_dav_svn, you should get an svnadmin
It is not unlikely that there is somewhere a second install of Subversion on
Having the same BDB version is more important than having the exact
I know many Windows tools use BDB 4.4.20, so that might be an easy way to
From: Dana Epp [mailto:dana_at_vulscan.com]
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
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
On Fri, Aug 16, 2013 at 1:37 PM, Dana Epp <dana_at_vulscan.com
I have inherited a REALLY old SVN server that was mismanaged for years. They
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
svn: bdb: DB_ENV->log_flush: LSN of 56874/862249 past current end-of-log of
Does anyone know where I should go from here? Does anyone know of anyone
-- Regards, Dana -- Regards, Dana Epp Microsoft Security MVPReceived on 2013-08-17 01:26:55 CEST
This is an archived mail posted to the Subversion Users mailing list.