Recovery failure

[James Montebello <ja...@quova.com>]

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

Re: Recovery failure

[Ben Collins-Sussman <su...@collab.net>]

James Montebello wrote:

> 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?

It sounds like you've got at least two completely unrelated problems:

1. your working copy had a "~", which, if you read 'svn help status", 
means that something is under version control, but a weird object is in 
its place.  Like, you scheduled a file for addition, but then before 
committing, replaced it with a dir or symlink or something.  All of the 
"not locked" errors coming from 'svn commit' are caused by this.  The 
fact that 'svn cleanup' says a directory is not a working copy makes me 
wonder if you didn't somehow delete some .svn/ areas by accident somehere.

2. did you actually have to do a repository recovery for any reason? 
Was the repository actually 'stuck'?  Or were you just experimenting, 
looking for things to fix that might be related to your working copy 
problems?  (Your commit problems had nothing to do with a wedged 
repository, just a messed up working copy.)


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org