Re: kill svn and working copy is corrupt

Jan Evert van Grootheest <j.grootheest@euronext.nl> writes:

> D:\svn\MAL\MAL\Dev\development\3rdparty\ACE\ACE_wrappers>svn up
> svn: Attempted to lock an already-locked dir
> svn: working copy locked: .
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
>
> D:\svn\MAL\MAL\Dev\development\3rdparty\ACE\ACE_wrappers>svn cleanup
> svn: Problem running log
> svn: in directory 'docs/tutorials/005'
> svn: The system cannot find the file specified.
> svn: svn_io_copy_file: error copying
> 'docs/tutorials/005/.svn/tmp/text-base/clie
> nt_handler.cpp.svn-base' to 'docs/tutorials/005/client_handler.cpp.tmp'

The wc journals are supposed to be idempotent; in other words, when
'svn cleanup' re-runs the journal, it should all just work, even if it
means re-running some journaled commands.

But we've seen an elusive win32 bug related to file i/o. The journal
obviously has a command to copy a specific .svn-base file to a .tmp
file, but the .svn-base file isn't present. This is probably that
mysterious win32 file i/o bug.

> How would one normally recover from this?

Exactly what you did below.

> I deleted the tutorials directory and removed it from
> docs/.svn/entries. After that cleanup completed succesfully and
> another update worked.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 4 16:16:40 2003