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

Re: Disconnection halfway through commit - files now 'obstructed'

From: Michael Abbott <mabster_at_internode.on.net>
Date: 2005-02-23 23:22:33 CET

Michael Abbott wrote:
> My friend has a repository on his machine with a berkeley backend. I
> connect to his machine, which is running through Apache. We're both
> using Windows, and using Tortoise to do the SVN work (this shouldn't
> contribute to this discussion ;). Today I committed a huge group of
> files to his repository, but halfway through the connection timed out
> (this does appear to happen occasionally). When I tried to commit again
> I discovered there were now problems. All the new files in the DB are
> considered to be 'obstructed' and I have no idea how to cancel my atomic
> operation. I assume this is possible from my end considering the nature
> of subversion :-) How do I do this?

After no replies and a bit of searching I've come across this item in
the FAQ:

"Every time I try to access my repository, the process just hangs. Is my
repository corrupt?"

I assume the item is talking about something similar to the obstructed
file problem. Of course, the repository isn't in a stuck state since my
friend can commit to it without any issues. But from my end, the
Berkeley DB journaling operation for my change was never completed, so I
need to remove the history of those incomplete operations somehow. Am I
on the right track?

I should also point out that the above commit operation was purely
'adds', if that affects this.

I assume that this is a fairly uncommon problem considering how little a
google search for "obstructed site:subversion.org" comes up with?

Thanks again,
- Mab

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 23 23:24:54 2005

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.