From users-return-5258-daniel=haxx.se@subversion.apache.org Fri Oct 8 18:20:21 2010 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on giant.haxx.se X-Spam-Level: X-Spam-Status: No, score=0.5 required=3.0 tests=BAYES_00,FREEMAIL_FROM, HTML_MESSAGE,T_DKIM_INVALID,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL autolearn=no version=3.3.1 Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by giant.haxx.se (8.14.3/8.14.3/Debian-9.1) with SMTP id o98GKKKx030089 for ; Fri, 8 Oct 2010 18:20:21 +0200 Received: (qmail 46538 invoked by uid 500); 8 Oct 2010 16:20:11 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 46529 invoked by uid 99); 8 Oct 2010 16:20:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Oct 2010 16:20:11 +0000 X-ASF-Spam-Status: No, hits=4.4 required=10.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL Received-SPF: pass (nike.apache.org: domain of res1413@gmail.com designates 209.85.214.43 as permitted sender) Received: from [209.85.214.43] (HELO mail-bw0-f43.google.com) (209.85.214.43) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Oct 2010 16:20:03 +0000 Received: by bwz11 with SMTP id 11so237810bwz.16 for ; Fri, 08 Oct 2010 09:19:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=9ch+2nXOwl44F8NTCOKLkcLrmLzTeKkcB21G4gUc30w=; b=OeErZpoJnhkgYEBe4UTPINwb0PtHbeAcaePWeWdmN4KL2GZUPbfdwI2RJJTkE6b4Zx o4HlyQyf63eSSQ02MVmLppcKyAPUjxtfcmzE2mZY7XO7qLTL/USL2TW1pxsHLkgkxEp+ X25uSWSyIqBDiYJ/QVIuD2xmlbHMQHRQ0CscQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=l5t7TrH2bbNWXTM6MqkUEePAgbUP5wo8itpFug4KpxnUmxBeKRAZh3kgwr1W12xMKE pr3ij52bzDkXqhC+G87zOesM81UjGAXY43dD1BiDbKtUP09W5AZwjYBJm0tdmJ2sxM8J TFq6IiTaIvsobcABP01Kl57145EXKTlhB2GXY= MIME-Version: 1.0 Received: by 10.204.177.79 with SMTP id bh15mr2234482bkb.121.1286554782226; Fri, 08 Oct 2010 09:19:42 -0700 (PDT) Received: by 10.204.32.202 with HTTP; Fri, 8 Oct 2010 09:19:42 -0700 (PDT) Date: Fri, 8 Oct 2010 12:19:42 -0400 Message-ID: Subject: Need help on Subversion dump/load feature....Thanks From: Reddy1413 To: users@subversion.apache.org Content-Type: multipart/alternative; boundary=0016e6d7effbc757f204921d60cd X-Virus-Checked: Checked by ClamAV on apache.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.3.5 (giant.haxx.se [80.67.6.50]); Fri, 08 Oct 2010 18:20:21 +0200 (CEST) X-Friend: Nope --0016e6d7effbc757f204921d60cd Content-Type: text/plain; charset=ISO-8859-1 Greetings, As part of the experiment with svn dump/load ,I am using svnadmin dump and load utilities on the same box. The dump and load provide some very nice features for making the migration of large-ish repositories a manageable task. My thanks to those responsible. However, am having trouble with an aspect of the load on the target migration system. Background: Am a relative newbie but have read the svn book particularly Repository Maintenance/Migrating Data Elsewhere (more than once, to be honest ; done a subversion software upgrade and a bit of other hands-on. To keep the dump file size "under control" am using both the -r switch to dump a range of revisions, and the --deltas switch for "compressed, binary differences" as the book says. For example, svnadmin dump /repos_path -r0:50 --deltas > repos_r0-50.dmp svnadmin dump /repos_path -r51:HEAD --deltas > repos_r51-HEAD.dmp et cetera... I moved the *dmp files where I want to load. Now, the moment of truth: The load appears to work fine for the rev 0-50 dump file. "Appears" because only svnlook history /repos-path has been used on the target system as a quick check to see that the intended revisions are listed. However, for the next dump file and contiguous set of revisions: svnadmin create target_repos_path svnadmin load /target_repos_path < repos_r0-50.dmp #worked fine no problem. svnadmin load /target_repos_path < repos_r51-HEAD.dmp #bouncer, Thrown error as below the above command returns nearly immediately and the following is output to stderr: <<< Started new transaction, based on original revision 51 svnadmin: File already exists: filesystem 'loadtest/db', transaction '50-1e', path 'proj16' * adding path : proj16 ... The /target_repos_path is named the same as the source /repos_path (fyi) The svn book says --deltas is useful and a dump using -r followed by svnadmin load in order from bottom up is supposed to work fine. So there must be something else about the dump switches or about the load that I do not understand or missed in the svn book. Thanks very much in advance for any illumination on the subject. --0016e6d7effbc757f204921d60cd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Greetings,=A0

As part of the experiment with = svn dump/load ,I am using svnadmin dump and load utilities on the same box.=

The dump and load provide some very nice features= for making the migration of large-ish repositories a manageable task. My t= hanks to those responsible. However, am having trouble with an aspect of th= e load on the target migration system.=A0

Background: Am a relative newbie but have read the svn = book particularly Repository Maintenance/Migrating Data Elsewhere (more tha= n once, to be honest =A0; done a subversion software upgrade and a bit of o= ther hands-on.=A0

To keep the dump file size "under control" am= using both the -r switch to dump a range of revisions, and the --deltas sw= itch for "compressed, binary differences" as the book says. For e= xample,=A0

svnadmin dump /repos_path -r0:50 --deltas > repos_r0= -50.dmp=A0
svnadmin dump /repos_path -r51:HEAD --deltas > repo= s_r51-HEAD.dmp=A0
et cetera...=A0

I move= d the *dmp files where I want to load.

Now, the moment of truth:=A0

T= he load appears to work fine for the rev 0-50 dump file. "Appears"= ; because only svnlook history /repos-path has been used on the target syst= em as a quick check to see that the intended revisions are listed.=A0

However, for the next dump file and contiguous set of r= evisions:=A0

svnadmin create target_repos_path
svnadmin load /target_repos_path < repos_r0-50.dmp =A0#worked fin= e no problem.
svnadmin load /target_repos_path < repos_r51-HEAD.dmp =A0#bouncer, = Thrown error as below

the above command returns ne= arly immediately and the following is output to stderr:=A0


<<< Started new transaction, based on original= revision 51
svnadmin: File already exists: filesystem 'loadt= est/db', transaction '50-1e', path 'proj16'
=A0=A0 =A0 * adding path : proj16 ...


The /target_repos_path is named the same as the source /repos_path (fyi)= =A0

The svn book says --deltas is useful and a dum= p using -r followed by svnadmin load in order from bottom up is supposed to= work fine.=A0

So there must be something else about the dump switches= or about the load that I do not understand or missed in the svn book.=A0

Thanks very much in advance for any illumination on= the subject.=A0
--0016e6d7effbc757f204921d60cd--