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

Re: svnadmin dump issue - E200015

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Thu, 11 Aug 2016 15:29:33 +0200

On Wed, Aug 10, 2016 at 6:43 PM, William Muriithi
<william.muriithi_at_gmail.com> wrote:
> Johan,
>>> - Is it safe to use svnadmin dump on the source repository? As in
>>> does it do it change in the source repo?
>> Yes, it's absolutely safe to run on the source repository, it should
>> not cause anything to change in the source repo.
> Thanks. What about "svnadmin verify /var/svn/projects" ?

That's a read-only operation too (just like svnadmin dump), so should
be perfectly safe. BTW, both 'svnadmin dump' and 'svnadmin verify'
should run without problems on a busy repository (it doens't interfere
with commits and other write or read operations that happen in

>>> - What causes E200015? I don't think its permission as I have even
>>> attempted to run svnadmin dump with root permissions? How can I
>>> overcome the issue?
>> Is that the full error message you gave?
> Yes, that was it. There was nothing else that it threw at standard
> error during the dump
>> "Caught signal" would be what you'd get if the process were aborted by
>> a signal, like aborting it with Ctrl-C, or if some other user with
>> enough permissions sends a kill signal to your process or something
>> like that.
>> Is it always aborting at the same revision?
> Yes, actually think its corruption related. I did manage dumping the
> repo in full but have not been able to restore it.

Hm, the fact that you *were* able to dump it in full (I guess by
splitting it up in chunks, as was suggested by Nico) indicates that
it's probably not a corruption in your source repository. The fact
that it works by dumping in chunks, but not in one giant dump, points
to a resource problem for creating or storing the giant dump.

> The restore fails
> with the same error.
> * editing path :
> condor/trunk/work/design/ic/library/kl_condor/kl_vco_curmir_1to20mA/starrc/layout.oa
> ... done.
> svnadmin: E200015: Caught signal

Here too I would guess you hit some system limit (RAM / swap space,
disk, maybe open file descriptors, ...). Perhaps you can split the
load process in even more steps, by specifying even smaller revision
ranges (but still using the dump files you created earlier). See
'svnadmin help load':

If --revision is specified, limit the loaded revisions to only those
in the dump stream whose revision numbers match the specified range.

Received on 2016-08-11 15:30:03 CEST

This is an archived mail posted to the Subversion Users mailing list.