I'm don't remember if this was already on the list or not, but didn't see it
in a scan through the archives, though I vaguely remember a thread of
something similar.
The scenario:
Uncompressing a large file on the Linux (Debian) server.
Committing some files from the (Windows XP) client.
Basically, the server was busy and the client commit operation timed out. I
figured that I would let the uncompressing finish and try it again the
following day. Now all operations that access that repository wait ... The
other repositories work just like always.
I suspect that it is a database related thing, so I am running svnadmin
recover repo. Any estimate on how long this should take? I am at revision
15 and there are about 1000 files ~200MB worth of data. It has already been
running for a couple of hours... Not much history would be lost if I have
to cream it and start over, but it would be preferable not to.
A network trace of the 'svn up' command shows the client sending a PROPFIND
packet. There is no more further information exchange after that request.
Thanks,
Brian S.
Windows
C:\>svn --version
svn, version 0.23.0 (r5962)
compiled May 19 2003, 20:00:14
Linux
fe406837:/var/log/apache2# svn --version
svn, version 0.23.0 (dev build)
compiled May 19 2003, 07:26:32
Copyright (C) 2000-2003 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
The following repository access (RA) modules are available:
* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.
- handles 'http' schema
- handles 'https' schema
* ra_local : Module for accessing a repository on local disk.
- handles 'file' schema
* ra_svn : Module for accessing a repository using the svn network protocol.
- handles 'svn' schema
fe406837:/var/log/apache2#
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 8 18:26:14 2003