[svk-users] Mirroring question/problem

[L. Mark Pilant]

> What I found wasw that svk bottomed out just as you described,

Good.  It isn't just me :-P

> but that rerunning "svk sync -a" caused it to continue from
> where it had stopped. If you try that, do you get further?

I haven't tried "svk sync -a", but just issuing the same command
again caused it to pick up from where it failed.  The only thing
I don't know is if the revision it was in the process of copying
and committing is/was complete.

In other words, using the giving the same "svk sync //mirror/Wireshark"
about a dozen times actually got the repository copied, but I'm
not sure if there is a way to actually verify the contents to make
sure it is really good.

One other observation.  The number of revisions committed before
failure seemed to vary.  Sometimes only about 100 revisions would
get committed and other times it would be several thousand.

- Mark