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

Recovering broken repository

From: Chris Jensen <cjensen_at_gmail.com>
Date: 2006-01-23 07:14:25 CET

I need some help recovering a repository that's gone in a pretty bad way.

The story:
At some point in December the partition containing the repository filled up.
I've now moved the repository to a new bigger partition, taken a
backup of the directory (with cp -a) and am attempting to recover it
I've tried runing:
  svnadmin verify
  svnlook youngest
  svnadmin dump
all of which seemed to hang, and couldn't be killed except with kill -9

I tried svnadmin recover and that looked promising, it was using CPU
and disk for about 5 minutes, but now it doesn't appear to be using
either (according to top), after 10 minutes of that, I tried killing
it, but again, needed -9

Unfortunately, it seems the backups of gone awry too. I'm trying to
dig up old backups, but they may or may not show up. So recovering
from the repository itself may be my only option.

I also have another smaller repository for which svnadmin verify returns
svnlook: Berkeley DB error for filesystem infra/db while opening 'nodes' table:
Cannot allocate memory

So I'm starting to suspect broken packages, and am going to try moving
the repository to another server to try recovery - is that a valid

Any suggestions?

The system:
Gentoo linux, kernel 2.6.7
The partition is reiserfs, the repository is about 2GB
The repository id using bdb fs
Subversion 1.2.3

Thanks in advance,

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 23 07:15:12 2006

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.