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

Recovery failure

From: James Montebello <jamesm_at_quova.com>
Date: 2004-03-27 00:19:47 CET

Running 1.0.0 on RedHat9, accessing it strictly through HTTP via
Apache2.

Everything ran fine for about three weeks (in test mode), being used for
a few small projects, mostly by one person. Today, a directory appeared
in svn stat with a '~' marker. svn info says it's scheduled to be added
(correct). svn commit says that directory is 'not locked', and fails.
I try svnadmin verify, and it aborts after running for awhile. I shut
down Apache, and run svnadmin recover, and it fails, saying I have to
run recover!

I upgrade to 1.0.1, and the text of the messages are changed, but still
no fix.

svn commit says that directory IS locked, and I should run svn cleanup.
svn cleanup says that directory is not a working copy directory.
svnadmin recover is still failing saying I have to run recover.

Doing a dump and load appeared to fix this (so far as I can tell), but
having the repository corrupt itself in this fashion doesn't exactly
give me the warm and fuzzies.

Theories? Comments?

james montebello -- quova, inc.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Mar 27 00:20:41 2004

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