Lukas Ruf <ruf@rawip.org> writes:
> I put all the repositories to a local hard-disk,
> re-created the problematic repository from scratch,
> tried a checkout via https,
> killed the svn client by 'kill -9' (because I had to disconnect temporarely),
> restarted the checkout later,
> and experienced the same problem: Linux killed the client by abort (at
> least I saw this message on screen).
>
> Hence my questions:
> - does 'killing a checkout process by -9' destroy the repository?
> - if so what is the best way to stop a large checkout?
No, what you did shouldn't affect the repository at all.
When you restarted the checkout, was the old (incomplete) working copy
still present, or did you restart absolutely fresh, with nothing in
the way? (Subversion is supposed to gracefully resume even if the wc
is partially present already, but there might be a bug in the
resumption code or something.)
> - svn has the atomic operations. Is it possible that it crashes due
> to linux' limits because it saves also very large files/directories
> first in memory (one directory contained approx. 1.5GB of data but I
> have only 1GB RAM) before it writes the checkout to the disk?
This seems unlikely -- Subversion tries pretty hard to be streamy.
> I stumbled over this idea when I realized that after the abort there
> were no data on disk.
I think we need transcripts and concrete details at this point.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 6 21:17:49 2004