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

svn switch failures

From: Tim Van Epps <tvanepps_at_efs-us.com>
Date: 2004-06-10 17:33:20 CEST

I am having constant problems with 'svn switch' failing.

I have a working copy called src/incl which contains roughly 300
directories and
3600 files. I originally used 'svn co' to populate this tree from a branch
copied from the trunk.

Today, in a different working copy checked out from the trunk, I added
one file and changed four others, all in the same directory. After
those files into the trunk, I created a branch. I then wanted to update my
src/incl so I used
    cd src/incl
    svn switch <new branch>/src/incl
After 5 minutes, my working copy is updated but the svn command reports
an error:

svn: REPORT request failed on '/repos/!svn/vcc/default'
svn: REPORT of '/repos/!svn/vcc/default': Could not read response body:
connection was closed by server. (http://svn1)

which causes my script to fail.

This is not a one-time problem. Several 'svn switch' commands have failed in
a similar fashion and the only work-around seems to be recreating src/incl
with 'svn co'; this, or course, resets all my file times which means
including these files must be rebuilt, which is why I want to use svn

Some questions:

1. is this the right way to update my working copy
2. what causes the errors printed above. My repository is on a linux box
   running svn1.0.3 and my commands and working copy are on a Solaris box
   running svn1.0.1
3. when I execute the 'svn switch', top reports that my Solaris box is
   roughly 97% iowaiting while the linux box is idle. Does that mean
   Is it related?

Tim Van Epps

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 10 17:35:01 2004

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.