Return-Path: 
 <users-return-24064-apmail-subversion-users-archive=subversion.apache.org@subversion.apache.org>
X-Original-To: apmail-subversion-users-archive@minotaur.apache.org
Delivered-To: apmail-subversion-users-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id B93F2188B0
	for <apmail-subversion-users-archive@minotaur.apache.org>;
 Wed, 25 Nov 2015 09:53:16 +0000 (UTC)
Received: (qmail 40171 invoked by uid 500); 25 Nov 2015 09:53:11 -0000
Delivered-To: apmail-subversion-users-archive@subversion.apache.org
Received: (qmail 40133 invoked by uid 500); 25 Nov 2015 09:53:11 -0000
Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@subversion.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@subversion.apache.org>
List-Post: <mailto:users@subversion.apache.org>
List-Id: <users.subversion.apache.org>
Delivered-To: mailing list users@subversion.apache.org
Delivered-To: moderator for users@subversion.apache.org
Received: (qmail 79725 invoked by uid 99); 25 Nov 2015 09:25:05 -0000
X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 2.879
X-Spam-Level: **
X-Spam-Status: No, score=2.879 tagged_above=-999 required=6.31
	tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
	HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01,
	SPF_PASS=-0.001] autolearn=disabled
Authentication-Results: spamd3-us-west.apache.org (amavisd-new);
	dkim=pass (2048-bit key) header.d=gmail.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=NWYI0w0q37VRfnFe+BpUxGD7kZsZHeM31+4CGRS9/pQ=;
        b=YhaUrcoW7Lm2a5+ylF8hPmNroTuUO3Jg+Rot7J2Jeh8OqgDL8YT9jed3lQjJsSLR+Q
         RmRSMeFjIsPamw7CLxgDsiyPiLUPJrThnM0pXWvkLKMKgE3bwovPBXpxqbsABEE5pk8R
         nsrsAriEklJ9YTSsrMG6O5hOwLbA9fHowVXHTxslvSp7cB/MkYdU5/BLViIZmjX0PT2g
         PokIjAj90m6uPjLJap1XhPd5qi8X4Tz6z5lRbwEQLvWeQUNoUSHYFoyIiBpMe2xL1ukQ
         WY7ZLS13uyzJNR4KkgB1ydfO8DSi0wRdn9IKZ/FG9y1u9C7GaSzh3i4yyRuwZEgXbgXV
         4ezw==
MIME-Version: 1.0
X-Received: by 10.31.44.77 with SMTP id s74mr31541157vks.4.1448443502688; Wed,
 25 Nov 2015 01:25:02 -0800 (PST)
Date: Wed, 25 Nov 2015 14:55:02 +0530
Message-ID: 
 <CAMF960RHvmraC=W2o9F2t_rAJeZvWiP=yjtT=EJcByvmw0eS=Q@mail.gmail.com>
Subject: SVN 1.6.17 dump is growing larger than repository size (approx. more
 than 10 times)
From: arun prasath <get2arun@gmail.com>
To: users@subversion.apache.org
Content-Type: multipart/alternative; boundary=001a11c075a274804105255a0893

--001a11c075a274804105255a0893
Content-Type: text/plain; charset=UTF-8

Hello Team,

I am creating Subversion 1.6.17 dump for a repository hosted in Linux
server. SVNSERVE is serving the repository. We are migrating to SVN 1.9.2.

*While creating the dump for repository of size 1.8 GB (revisions 3000+),
the dump command completes revision 119 and hangs and keep updating the
dumpfile which grows to 7-8 GBs. dump command is not moving to next
revision but kept updating the dump file. So, i just closed the putty to
stop creating the dump.*

However, I ran the svnadmin verify which completes revision 119 and take
some time to verify revision 120 and complete the verification successfully
for all the repository revisions.

Since, there is no error output I have no logs to attach. Please suggest
the work around for this situation. How can create the dump and migrate to
target server. I am planning to use rsync from the server. I will post how
it goes.

I am expecting the workaround to this situation and let me know if this is
a known issue in SVN 1.6.17. This is my active repository and created the
dump without stopping the svnserve program in the production server.


Thanks,
Arun

--001a11c075a274804105255a0893
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hello Team,</div><div><br></div><div><div>I am creati=
ng Subversion 1.6.17 dump for a repository hosted in Linux server. SVNSERVE=
 is serving the repository. We are migrating to SVN 1.9.2.</div><div><br></=
div><div><b>While creating the dump for repository of size 1.8 GB (revision=
s 3000+), the dump command completes revision 119 and hangs and keep updati=
ng the dumpfile which grows to 7-8 GBs. dump command is not moving to next =
revision but kept updating the dump file. So, i just closed the putty to st=
op creating the dump.</b></div><div><br></div><div><font color=3D"#38761d">=
However, I ran the svnadmin verify which completes revision 119 and take so=
me time to verify revision 120 and complete the verification successfully f=
or all the repository revisions.</font></div><div><br></div><div>Since, the=
re is no error output I have no logs to attach. Please suggest the work aro=
und for this situation. How can create the dump and migrate to target serve=
r. I am planning to use rsync from the server. I will post how it goes.</di=
v><div><br></div><div>I am expecting the workaround to this situation and l=
et me know if this is a known issue in SVN 1.6.17. This is my active reposi=
tory and created the dump without stopping the svnserve program in the prod=
uction server.=C2=A0</div></div><div><br></div><div><br></div><div>Thanks,<=
/div><div>Arun</div></div>

--001a11c075a274804105255a0893--