working copy corruption when network connection lost

Hi

I have been experiencing network problems recently. These are nothing
to do with subversion, however they do cause the subversion client to
time-out. On one occasion this occurred while running 'svn up' on a
subversion working copy. This left the subversion/bindings working
copy in a corrupt state:

$ svn st -u svn-broke/subversion/bindings/

apr_error: #20014, src_err 0 : <Error string not specified yet>
  The REPORT status was 500, but expected 200.

I cannot update it either:

$ svn up svn-broke/subversion/bindings/

apr_error: #20014, src_err 0 : <Error string not specified yet>
  The REPORT status was 500, but expected 200.

The following command appears to work:

$ svn st -un svn-broke/subversion/bindings/
_ * 721 svn-broke/subversion/bindings
_ * 721 svn-broke/subversion/bindings/README
_ * 721 svn-broke/subversion/bindings/apr.i
_ * 721 svn-broke/subversion/bindings/svn_client.i
_ * 721 svn-broke/subversion/bindings/svn_delta.i
_ * 721 svn-broke/subversion/bindings/svn_fs.i
_ * 721 svn-broke/subversion/bindings/svn_ra.i
_ * 721 svn-broke/subversion/bindings/svn_repos.i
_ * 721 svn-broke/subversion/bindings/svn_string.i
_ * 721 svn-broke/subversion/bindings/svn_types.i
_ * 721 svn-broke/subversion/bindings/svn_wc.i
_ * 721 svn-broke/subversion/bindings/util.i
Head revision: 728

I am not quite sure where the problem lies but I suspect the
.svn/entries file is corrupt. Revision 724 created the bindings/swig
subdirectory and moved the above files into it. The suspect entries
file contains both the new subdirectory and the files that should have
been moved. Thus I suspect that the network connection failed during
the processing of this part of the delta.

Now in this particular case, since I have no local changes, I can
solve the problem by simply discarding the directory, and checking out
a new version. However if I had made local changes this would not be
so simple, and in these circumstances I would not trust 'svn diff'. I
guess I would resort to checking out a new version and manually
comparing the hierarchies.

The best solution would be to have commit/rollback semantics on the
working copy, but I don't know if this is feasible. Does cvs suffer
from the same problem?

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