[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Is it possible to upgrade an older db version?

From: Max Bowsher <maxb_at_ukf.net>
Date: 2004-08-10 20:38:47 CEST

Bryan Donlan wrote:
> On Tue, 10 Aug 2004 14:10:08 +0100, Maurice R. Kelly
> <subversion@chatswood.org.uk> wrote:
>> Max Bowsher wrote:
>>
>>> Maurice R. Kelly wrote:
>>>
>>>> From what I've read in this list's archives (and other places) it seems
>>>> that I'm probably looking at an incompatibility between db versions
>>>> (I've created a new test repos and it interacts fine with Apache). I'm
>>>> now running 4.1.25 but in fitting with my luck, I have no idea what the
>>>> previous version was.
>>>
>>>
>>> od -A d -t d4 /path/to/repos/db/__db.001 | less
>>>
>>> Look through the output. Somewhere in the first 200 bytes or so, you
will
>>> see one of the sequences:
>>> 4 0 14
>>> 4 1 25
>>> 4 2 52
>>
>> Okay - my old repositories appear to use 4.2.52:
>> 0000032 0 4 2 52
>>
>>> Now you've done that, you (compile | find a precompiled binary of)
>>> subversion linked with the appropriate BDB version.
>>
>> Right, I'll try to obtain (source or binary) BDB 4.2.52 and compile it
>> up. Can I use some of the tools provided by BDB in order to produce the
>> dump (as I presume Subversion simply wraps around DBD routines when
>> producing dumps)?
>
> Subversion uses its own dump format - it's designed to be independent
> of any particular method of storing the actual data, so it can be used
> for things like converting to fsfs.

That's true.

> So you'll have to compile
> subversion with BDB 4.2.52.

But this isn't.

If you really want to, you could use something like this:

cd repository
mv db 42_db
mkdir db
cp 42_db/DB_CONFIG db/
cp 42_db/fs-type db/ # if it exists
cd 42_db
for i in *s; do
  db4.2_dump $i | db4.1_load -h ../db $i
done
cd ..
svnadmin recover .

NOTE: Since you just started a BDB transactional logging environment with
content pre-loaded into the database tables, a complete set of log.000*
files from 1 to the end is *not* a complete backup in this case.

HOWEVER: You probably should compile subversion against 4.2.52, *and use it
in preference to your current svn w/ 4.1.25*. The general experience among
subversion users has been that 4.2 is noticably more stable than 4.1.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 10 20:39:34 2004

This is an archived mail posted to the Subversion Users mailing list.