-----Original Message-----
From: Philip Martin [mailto:philip@codematters.co.uk]
Sent: Thursday, August 21, 2003 8:16 PM
To: Steve Dwire
Cc: users@subversion.tigris.org
Subject: Re: WC locked. Can't cleanup: .svn/tmp/text-base is empty
> "Steve Dwire" <sdwire@pcsigroup.com> writes:
>
>> 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'
And here's the log file immediately after:
------------------------
<mv
dest=".svn/props/E1B7083C8F074A84B3D99F8EE015FFF8.xml.svn-work"
name=".svn/tmp/props/E1B7083C8F074A84B3D99F8EE015FFF8.xml.svn-work"/>
<readonly
name=".svn/props/E1B7083C8F074A84B3D99F8EE015FFF8.xml.svn-work"/>
<mv
dest=".svn/prop-base/E1B7083C8F074A84B3D99F8EE015FFF8.xml.svn-base"
name=".svn/tmp/prop-base/E1B7083C8F074A84B3D99F8EE015FFF8.xml.svn-base"/
>
<readonly
name=".svn/prop-base/E1B7083C8F074A84B3D99F8EE015FFF8.xml.svn-base"/>
<modify-entry
committed-rev="1"
name="E1B7083C8F074A84B3D99F8EE015FFF8.xml"/>
<modify-entry
name="E1B7083C8F074A84B3D99F8EE015FFF8.xml"
committed-date="2003-08-21T04:30:53.952125Z"/>
<modify-entry
name="E1B7083C8F074A84B3D99F8EE015FFF8.xml"
committed-date="2003-08-21T04:30:53.952125Z"/>
<modify-entry
committed-rev="1"
name="E1B7083C8F074A84B3D99F8EE015FFF8.xml"/>
<modify-entry
name="E1B7083C8F074A84B3D99F8EE015FFF8.xml"
uuid="8ae5b214-e036-ab4c-80bd-f902e0739445"/>
<modify-entry
name="E1B7083C8F074A84B3D99F8EE015FFF8.xml"
kind="file"
deleted="false"
revision="1"/>
<cp-and-translate
dest="E1B7083C8F074A84B3D99F8EE015FFF8.xml"
name=".svn/tmp/text-base/E1B7083C8F074A84B3D99F8EE015FFF8.xml.svn-base"/
>
<modify-entry
name="E1B7083C8F074A84B3D99F8EE015FFF8.xml"
text-time="working"/>
<modify-entry
name="E1B7083C8F074A84B3D99F8EE015FFF8.xml"
prop-time="working"/>
<mv
dest=".svn/text-base/E1B7083C8F074A84B3D99F8EE015FFF8.xml.svn-base"
name=".svn/tmp/text-base/E1B7083C8F074A84B3D99F8EE015FFF8.xml.svn-base"/
>
<readonly
name=".svn/text-base/E1B7083C8F074A84B3D99F8EE015FFF8.xml.svn-base"/>
<modify-entry
name="E1B7083C8F074A84B3D99F8EE015FFF8.xml"
checksum="4f1b19e44f068b193e70e7d821580d35"/>
<modify-wcprop
name="E1B7083C8F074A84B3D99F8EE015FFF8.xml"
propname="svn:wc:ra_dav:version-url"
propval="/repos/!svn/ver/1/Dest/DocStore/Data%20Documents/Physicians/E1B
7083C8F074A84B3D99F8EE015FFF8.xml"/>
------------------------
>> One of my directories has >3200 files in it. When I look at my
>> working copy, it has fewer than 2200. No problem, I say to myself.
>> I'll just hit update again and see if it gets it up to date. Of
>> course, I hit the classic "working copy is locked" issue. I remember
>> seeing that in the FAQ, so I discover the svn cleanup command.
>>
>> When I type svn cleanup C:\test, I get the following:
>>
>> C:\>svn cleanup C:\test
>> svn: Problem running log
>> svn: in directory 'C:/test/Dest/DocStore/Data Documents/Physicians'
>
> It would be interesting to see the contents of the log file, you
> should find it at .../Physicians/.svn/log
Embedded
----------------------
<mv
dest=".svn/props/713FABD831C4441CB4272DC2E292F990.xml.svn-work"
name=".svn/tmp/props/713FABD831C4441CB4272DC2E292F990.xml.svn-work"/>
<readonly
name=".svn/props/713FABD831C4441CB4272DC2E292F990.xml.svn-work"/>
<mv
dest=".svn/prop-base/713FABD831C4441CB4272DC2E292F990.xml.svn-base"
name=".svn/tmp/prop-base/713FABD831C4441CB4272DC2E292F990.xml.svn-base"/
>
<readonly
name=".svn/prop-base/713FABD831C4441CB4272DC2E292F990.xml.svn-base"/>
<modify-entry
committed-rev="1"
name="713FABD831C4441CB4272DC2E292F990.xml"/>
<modify-entry
name="713FABD831C4441CB4272DC2E292F990.xml"
committed-date="2003-08-21T04:30:53.952125Z"/>
<modify-entry
name="713FABD831C4441CB4272DC2E292F990.xml"
committed-date="2003-08-21T04:30:53.952125Z"/>
<modify-entry
committed-rev="1"
name="713FABD831C4441CB4272DC2E292F990.xml"/>
<modify-entry
name="713FABD831C4441CB4272DC2E292F990.xml"
uuid="8ae5b214-e036-ab4c-80bd-f902e0739445"/>
<modify-entry
name="713FABD831C4441CB4272DC2E292F990.xml"
kind="file"
deleted="false"
revision="1"/>
<cp-and-translate
dest="713FABD831C4441CB4272DC2E292F990.xml"
name=".svn/tmp/text-base/713FABD831C4441CB4272DC2E292F990.xml.svn-base"/
>
<modify-entry
name="713FABD831C4441CB4272DC2E292F990.xml"
text-time="working"/>
<modify-entry
name="713FABD831C4441CB4272DC2E292F990.xml"
prop-time="working"/>
<mv
dest=".svn/text-base/713FABD831C4441CB4272DC2E292F990.xml.svn-base"
name=".svn/tmp/text-base/713FABD831C4441CB4272DC2E292F990.xml.svn-base"/
>
<readonly
name=".svn/text-base/713FABD831C4441CB4272DC2E292F990.xml.svn-base"/>
<modify-entry
name="713FABD831C4441CB4272DC2E292F990.xml"
checksum="2757dd39962b01d288c9f756efcd02a2"/>
<modify-wcprop
name="713FABD831C4441CB4272DC2E292F990.xml"
propname="svn:wc:ra_dav:version-url"
propval="/repos/!svn/ver/1/Dest/DocStore/Data%20Documents/Physicians/713
FABD831C4441CB4272DC2E292F990.xml"/>
--------------------------------
>> svn: The system cannot find the file specified.
>> svn: svn_io_copy_file: error copying 'C:/test/Dest/DocStore/Data
>> Documents/Physicians/.svn/tmp/text-base/713FABD831C4441CB4272DC2E292F
>> 990
>> .xml.svn-base' to 'C:/test/Dest/DocStore/Data
>> Documents/Physicians/713FABD831C4441CB4272DC2E292F990.xml.2.tmp'
>>
>> So I decided to do some spelunking, and I find that
>> .../Physicians/.svn/tmp/text-base is empty. No wonder svn cleanup
>> couldn't find the file specified. Now I've reached the end of the
>> FAQ, so I find myself at your mercy.
>>
>> How can I recover from this?
>
>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)
I suppose I could zap the whole C:/test and start over, but I'd rather
not do something that drastic unless it's the only choice I have left.
S_E_D
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 22 05:18:44 2003