[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: Sun, 7 Aug 2016 22:45:32 +0200

On Sun, Aug 7, 2016 at 8:41 PM, William Muriithi
<william.muriithi_at_gmail.com> wrote:
> Hello,
> I have a repository thats around 113 GB in size. Its on a VM and the
> performance hasn't been that ideal. So we decided to source a new
> hardware and set it up on its own dedicated system.
> The current subversion system is subversion-1.8, and plan to move it
> to subversion-1.9. I have en
> source server:
> subversion-1.8.13-1.x86_64
> I have attemped svnadmin dump, svnadmin hotcopy and svnrdump. I am
> getting the error before from all these utilities
> svnadmin: E200015: Caught signal
> or
> * Dumped revision 2968.
> svnrdump: E200015: Caught signal
> My two questions are:
> - 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.

> - 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?

"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?

Maybe someone else is interfering with your work, and (accidently)
killing your process? Or maybe your remote (ssh / whatever) session
gets disconnected which causes the dump process to abort?

Received on 2016-08-07 22:46:03 CEST

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