Return-Path: 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 129A9186FC for ; Fri, 29 Jan 2016 10:43:02 +0000 (UTC) Received: (qmail 66673 invoked by uid 500); 29 Jan 2016 10:43:01 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 66636 invoked by uid 500); 29 Jan 2016 10:43:01 -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 66606 invoked by uid 99); 29 Jan 2016 10:43:01 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jan 2016 10:43:01 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 0920DC0D8E for ; Fri, 29 Jan 2016 10:43:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.88 X-Spam-Level: ** X-Spam-Status: No, score=2.88 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, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id RwSy1qQlvNJU for ; Fri, 29 Jan 2016 10:42:54 +0000 (UTC) Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com [74.125.82.44]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 3D5BB20C6A for ; Fri, 29 Jan 2016 10:42:54 +0000 (UTC) Received: by mail-wm0-f44.google.com with SMTP id p63so62217383wmp.1 for ; Fri, 29 Jan 2016 02:42:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KvYy3X7RlEhpY4o4SdN6N1ijrLOqUfQfStMI6fxHlr8=; b=xShdftbRvTTIU/XGk4E6dONZtP2L49YFHnn2P/uoxukIreGzu06sYqoKUsQDIcjjDH 2EfkLAXGAKknb9Qn5GOLRVT4TudV+1eyy+waT1R8Zc6Ok821ZCuZe6Ay5G7N/8+naUQv PLibfNy3TYaNj/SOZe55KwMBLae0kZuX4cYgKYCbgHWRyEDFvz9w9fW20Lzf539pA+Z8 8X/WK50iTo34yC3/y7lwcQt+iW9MBvG1GbCGED/Ig41av7LAg6jCAY/teXB1VnajzZdy PG/2m6Z9NBCdkN8lujEGJL0oDeOWsK2B+Rm+AYuNHmEQ3J4yIn2y+JmExJZya1W083E4 V2sA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=KvYy3X7RlEhpY4o4SdN6N1ijrLOqUfQfStMI6fxHlr8=; b=d+gytF0Kr9IFEEuD7B64tjPrRTjCAOncNnh1L2h3yipK9I4WCmZ2cMcpDQ+7MgGBU+ ZoEkalrnOKvzs60pKlzudAVup0vAQl9Px3a53vodEVqSRYcAFzA/bFm16DuG8oPjuy5c sOcMT0n08o15jB4PxzqsACnaYEgiNjGShdaMcVNWV67yXHiNzPA/bLABz62f132KyQGu iF38ewFSRrbPNuckYBhAfyznMM9fASN/Z1jp4CwzKNRQURjM61QhRudmxhAqxwR1u1L9 EX27PfPpWJC3S9aUkbb+hHlSeKvxBnY6FOonZjeSvfwYYjV3ABhs5Q61Zkaoo+GDkdaS yknA== X-Gm-Message-State: AG10YOTd9PEUD17HMFFnqsZG0yR0ueRFwUDM9QzvVrhYyPX4ZMaH6FrCwuWZJTIQormfEslOK5+/BzvEhzK92g== MIME-Version: 1.0 X-Received: by 10.194.173.233 with SMTP id bn9mr7843853wjc.1.1454064173980; Fri, 29 Jan 2016 02:42:53 -0800 (PST) Received: by 10.28.135.203 with HTTP; Fri, 29 Jan 2016 02:42:53 -0800 (PST) In-Reply-To: <87si1gr9vf.fsf@wandisco.com> References: <878u39ev70.fsf@wandisco.com> <878u39i5fb.fsf@wandisco.com> <87si1gr9vf.fsf@wandisco.com> Date: Fri, 29 Jan 2016 12:42:53 +0200 Message-ID: Subject: Re: Svn 1.9 repository 20% bigger than svn 1.8 repository From: Gert Kello To: Philip Martin Cc: "users@subversion.apache.org" Content-Type: multipart/alternative; boundary=089e0122f08892246d052a76b2d6 --089e0122f08892246d052a76b2d6 Content-Type: text/plain; charset=UTF-8 On 29 January 2016 at 11:52, Philip Martin wrote: > > How can I test if the 1.9 has really corrupt sqlite db file? For me it > > seems that it still gets updates (i.e. when I bring in new revisions with > > svnsync.) > > Check the index with: > > sqlite3 db/rep-cache.db "pragma integrity_check" > Says "ok" > Compare the ordered list: > > sqlite3 db/rep-cache.db "select hash,revision from rep_cache order by > revision" > > with the 1.8 list and you may be able to identify which revisions are > missing from the 1.9 rep-cache. There isn't any way to fix the missing > They are identical up to rev 91450. And then there's a large gap between revisions 91450 and 155838. 155838 seems to be where new "svnsync" was started, there's gap of time stamps in revision files. 91450 does not seem to be special in term of sync sequence. About 60 revisions within same minute, previous two in same second, next one 4 seconds later (How does svnsync work? "find last rev at source and sync up to that" or "sync while next revision present in source"? If latter then first sync failed for some reason... If first then it probably ran till completion. But does it actually matter?) > deduplication other than a dump/load, but it would be interesting to > find out why it failed. Should I look at some svn oog information about the revisions where is started to fail? Anything special to look for? Or should we assume "antivirus or something else opened the file so that svnsync was unable to write it"? The sync for this rev has been executing in the middle of day so it is possible I tried to peek "how big the repo is at disk". > Which method did you use to write during sync: > file, svn or http? > file:/// Gert --089e0122f08892246d052a76b2d6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 29 January 2016 at 11:52, Philip Martin <philip.martin@wandisc= o.com> wrote:
> How can I test if the 1.9 has really corrupt sq= lite db file? For me it
> seems that it still gets updates (i.e. when I bring in new revisions w= ith
> svnsync.)

Check the index with:

=C2=A0 sqlite3 db/rep-cache.db "pragma integrity_check"

Says "ok"
=C2=A0
Compare the ordered list:

=C2=A0 sqlite3 db/rep-cache.db "select hash,revision from rep_cache or= der by revision"

with the 1.8 list and you may be able to identify which revisions are
missing from the 1.9 rep-cache.=C2=A0 There isn't any way to fix the mi= ssing

They are identical up to rev 91450. And th= en there's a large gap between revisions 91450 and 155838. 155838 seems= to be where new "svnsync" was started, there's gap of time s= tamps in revision files.
91450 does not seem to be special i= n term of sync sequence. About 60 revisions within same minute, previous tw= o in same second, next one 4 seconds later

(How does svnsync work? &= quot;find last rev at source and sync up to that" or "sync while next revision present in source"? If latter then fir= st sync failed for some reason... If first then it probably ran till=20 completion. But does it actually matter?)
=C2=A0
deduplication other than a dump/= load, but it would be interesting to
find out why it failed.=C2=A0

Should I loo= k at some svn oog information about the revisions where is started to fail?= Anything special to look for? Or should we assume "antivirus or somet= hing else opened the file so that svnsync was unable to write it"? The= sync for this rev has been executing in the middle of day so it is possibl= e I tried to peek "how big the repo is at disk".
= =C2=A0
Which method = did you use to write during sync:
file, svn or http?

file:///


Gert
=

--089e0122f08892246d052a76b2d6--