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

unable to do svnadmin dump

From: Vidar <vl-list_at_ez.no>
Date: 2003-08-28 15:19:42 CEST


I have a svn repository that seems partialy crashed.. I have test to do some
checkouts and that works, but am unable to dump the repository like this:
$ svnadmin dump nextgen > svn.dump

It stops on revision 85 with the following output:
svn: Filesystem has no such string
svn: locate_key: no such string `1e8'

The repository is rather big (3.4G, 3251 revisions)

"svnadmin recover" seems to run forever. (I look in /proc/[pid]/fd and
observers that svnadmin starts on a new file now and then, but in it's
current speed it will take a day or two before it have done them all.)

So I am wondering if I can saftely recover the svn repository this way:
- do a dump from an old binary backup, like this :
$cd backup
$svnadmin dump nextgen -r 0:2000 > old_backup.dump
- then dump the latest revision from my "live" repository:
$cd ../svnrepository
$svnadmin dump nextgen -r 2001:head > latest_revistions.dump

Can I then catenate old_backup.dump and latest_revistions.dump and import
this into a new repository ?
It seems reasonable but does anyone know for sure that this will work ?

I am using subversion-0.23.0-5972 and need a dump in order to upgarde to 0.28
Any help is appreciated

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 28 15:20:43 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.