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

RE: WC locked. Can't cleanup: ... (with original error message and log files)

From: Steve Dwire <sdwire_at_pcsigroup.com>
Date: 2003-08-24 05:48:08 CEST

Philip Martin <philip@codematters.co.uk> wrote:

>>>> Everything's going swimmingly until the update hits a snag with a
io
>>>> error.
>>>
>>> You haven't given us this error message, it's important as it's the
>>> one that triggered the problem. Which version of the Subversion
>>> client are you using?
>>
>> I'm using 0.26.0. It's the one with the Windows.exe installer. I
>> started over checking out to another directory to see if I could
>> reproduce the problem. Here's the error message:
>>
>> svn_io_file_rename: can't move 'C:/SVNTest/Dest/DocStore/Data
>> Documents/Physicians/.svn/tmp/entries' to
'C:/SVNTest/Dest/DocStore/Data
>> Documents/Physicians/.svn/entries'
>
> Was there an "Access is denied" message as well? This looks like the
> Subversion on Windows filesystem problem. Nobody appears able to
> reproduce the problem outside Subversion, which makes it difficult to
> fix. There was a patch to retry operations that fail, but that is a
> bit of a hack until we are sure about the root cause of the problem.

I believe there was an "Access is denied" message along with the "can't
move".

> The error message you have given refers to the entries file, the
> previous cleanup error referred to missing text base. Does the
> entries error above lead to the original text base error when you
> cleanup?

Yes. The entries failure came first. When I tried to recover from that
with svn cleanup, that's when I got the problem with the empty
text-base.

>>>The most reliable way to recover is to use ordinary OS operations to
>>>delete (or move) the Physicians directory from the working copy and
>>>then run update. Please look for the log file *before* deleting
>>>Physicians.
>>
>> I tried that, but the working copy was still locked, so I had to run
svn
>> cleanup first. That finished without complaining, but then a
subsequent
>> update gives me this:
>>
>> C:\>svn update C:\test
>> svn: Working copy not locked
>> svn: directory not locked (C:/test/Dest/DocStore/Data
>> Documents/Physicians)
>
> Nasty, I'll take this bit to the dev list.

I'd be grateful. I'm looking to convince my corporate cronies to use
Subversion (vs. SourceSafe or manual filesystem archives), and that's
hard to do when I can't get it working. :-(

S_E_D

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Aug 24 07:25:14 2003

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