search

RexZhang4321 / tortoisesvn

Automatically exported from code.google.com/p/tortoisesvn
0 stars 0 forks source link

"svn update" fails, leaves local checkout in inconsistent state #403

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I'm trying to check out a large repo (greater than 750 GB). After some time 
(the amount of time seems uncorrelated), the SSL/TLS connection times out and 
the checkout fails. I can get anywhere from 2GB to 20GB or 40GB per try.

Once the checkout fails, I cannot simply "svn update" again. When Tortoise 
fails, it leaves the svn database in an inconsistent state and I have to run a 
cleanup. It's usually not a big deal, but a large repo wastes a lot of time 
running the cleanup.

It would be great if Tortoise SVN cleaned up properly on an error so I don't 
have to perform a manual clean when an error is encountered.

Original issue reported on code.google.com by noloa...@gmail.com on 29 Aug 2012 at 5:26

Attachments:

GoogleCodeExporter commented 9 years ago 
The issues happens from both the command line and the GUI. I suspect its the 
Cisco VPN concentrator or file server on the other side of the pipe shitting 
all over itself.

Command Line Information:
C:\Users\jwalton>svn help
usage: svn <subcommand> [options] [args]
Subversion command-line client, version 1.7.6.
...

GUI Information:
TortoiseSVN 1.7.8, Build 23174 - 64 Bit , 2012/08/13 19:49:45
Subversion 1.7.6, 
apr 1.4.6
apr-utils 1.3.12
neon 0.29.6
OpenSSL 1.0.1c 10 May 2012
zlib 1.2.7

Original comment by noloa...@gmail.com on 29 Aug 2012 at 5:30

GoogleCodeExporter commented 9 years ago 
For the reasons described on the issue tracker main page
(http://code.google.com/p/tortoisesvn/wiki/IssueTracker?tm=3)
please do not file issues without being told to do so by
one of the developers on our mailing list users@tortoisesvn.tigris.org or use
the forum for the mailing list here:
http://tortoisesvn.tigris.org/ds/viewForumSummary.do?dsForumId=4061

In accordance with our guidelines I'm closing this issue as NotDiscussed.
Please post your questions to the users@ mailing list before filing an issue.
If one of the developers on the mailing list agrees that your issue is valid,
we will reopen this issue.

Original comment by tortoisesvn on 29 Aug 2012 at 5:44

GoogleCodeExporter commented 9 years ago 
> In accordance with our guidelines I'm closing this issue as NotDiscussed.
No problem. Your shit is still broken.

Original comment by noloa...@gmail.com on 29 Aug 2012 at 5:53