Return-Path: 
 <users-return-21717-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 EE2E911578
	for <apmail-subversion-users-archive@minotaur.apache.org>;
 Mon,  7 Jul 2014 11:15:08 +0000 (UTC)
Received: (qmail 24626 invoked by uid 500); 7 Jul 2014 11:15:03 -0000
Delivered-To: apmail-subversion-users-archive@subversion.apache.org
Received: (qmail 24593 invoked by uid 500); 7 Jul 2014 11:15:03 -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
Received: (qmail 24583 invoked by uid 99); 7 Jul 2014 11:15:03 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jul 2014 11:15:03 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of brane@wandisco.com designates
 74.125.82.182 as permitted sender)
Received: from [74.125.82.182] (HELO mail-we0-f182.google.com) (74.125.82.182)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jul 2014 11:14:58 +0000
Received: by mail-we0-f182.google.com with SMTP id q59so4251936wes.27
        for <users@subversion.apache.org>;
 Mon, 07 Jul 2014 04:14:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=wandisco.com; s=gapps;
        h=message-id:date:from:organization:user-agent:mime-version:to:cc
         :subject:references:in-reply-to:content-type
         :content-transfer-encoding;
        bh=8AvPV392DonIFr3j71FtNpNEMUWfnhb1kgUCY1ovOwI=;
        b=mM4AtIP1xYMtP+pqeiCqh9Jn5Y/+lHfmp+SVPP9KLcOXlKfGD314x6YvP2GrgxeAdx
         3bLcFx6SXb+gb2oKU/jE52qp8o4h1LM5bWR9ziua5evsYLG8u/uM45qNaK5zGIIAIwd4
         cAeDKXUW01GvxkX9XW+048FPo7N0nVKkOLqUk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:message-id:date:from:organization:user-agent
         :mime-version:to:cc:subject:references:in-reply-to:content-type
         :content-transfer-encoding;
        bh=8AvPV392DonIFr3j71FtNpNEMUWfnhb1kgUCY1ovOwI=;
        b=buwMIDK1OvBqqbEUThbP4VxM72a98SiRl1Rov0aJKp9b22p3zQhquUaJFl4AIgc5M1
         c37Hm3Z+zZMS01Q+US0YdKHjxX2Ym0FfbhsToABrLK+5cVRzhmN4T3AUK1p11PryRFGK
         bNvkysyw3iVPzHanIJsTSVB9HhvKm0ENcHCVxe7om/lUpUAQz+FDt/8A8xu7o98J2h7D
         hOhQzs9uqmYBMA5e3X4rVSvyf655iGjIzU09N2MBL3lpquQ9K5Dtgp5mcQErOprRMJI5
         +8tZfltX64WqgDrnquZvf+GOxcr3swenhGT28Z8zxubSEPz4s/ZI02xMDKmUiCAmdZQE
         OkeQ==
X-Gm-Message-State: 
 ALoCoQk6/iJRIJig7CjRqAbRcRrMHMeLAgm58qXf+q2ynKwf0rIVgTigbat+ya6loB1ve3L1oWZF
X-Received: by 10.180.75.47 with SMTP id z15mr22535439wiv.80.1404731676222;
        Mon, 07 Jul 2014 04:14:36 -0700 (PDT)
Received: from zulu.local (cpe-46-164-37-44.dynamic.amis.net. [46.164.37.44])
        by mx.google.com with ESMTPSA id
 d4sm96500589wik.20.2014.07.07.04.14.34
        for <multiple recipients>
        (version=TLSv1 cipher=RC4-SHA bits=128/128);
        Mon, 07 Jul 2014 04:14:35 -0700 (PDT)
Received: from zulu.local (localhost [IPv6:::1])
	by zulu.local (Postfix) with ESMTP id 1BFBBB37C001;
	Mon,  7 Jul 2014 13:14:33 +0200 (CEST)
Message-ID: <53BA8119.1040601@wandisco.com>
Date: Mon, 07 Jul 2014 13:14:33 +0200
From: =?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@wandisco.com>
Organization: WANdisco
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Nico Kadel-Garcia <nkadel@gmail.com>
CC: Subversion <users@subversion.apache.org>
Subject: Re: Subversion 1.8.9 repository access issue [Urgent]
References: 
 <CALL-kDdukyrLJGJcekGRG_NYz-HH=ewEHKzNTAH_=Ciy55cu1A@mail.gmail.com>
	<53B93485.4000404@gmx.de>	<53B9B873.2090603@wandisco.com>
	<53B9C57E.5030901@gmx.de>	<53BA4B06.4000504@wandisco.com>
 <CAOCN9rxOLHd8N83Cn4c1hGLEUH3jfsXvG-jmNjFe=1xEYjUqVA@mail.gmail.com>
In-Reply-To: 
 <CAOCN9rxOLHd8N83Cn4c1hGLEUH3jfsXvG-jmNjFe=1xEYjUqVA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Virus-Checked: Checked by ClamAV on apache.org

On 07.07.2014 12:48, Nico Kadel-Garcia wrote:
> On Mon, Jul 7, 2014 at 3:23 AM, Branko Čibej <brane@wandisco.com> wrote:
>> On 06.07.2014 23:54, Andreas Stieger wrote:
>>
>> On 06/07/14 21:58, Branko Čibej wrote:
>>
>> On 06.07.2014 13:35, Andreas Stieger wrote:
>>
>> Your repository is of type bdb, (berkeley db backend), not fsfs. As such
>> is it not suitable for a direct upgrade.
>>
>> That's nonsense.
>>
>> See DB_VERSION_MISMATCH and others. Building the bdb backend might just
>> uncover that.
>>
>>
>> The error in the httpd log is SVN_ERR_FS_UNKNOWN_FS_TYPE. So the part about
>> the BDB back-end not being built is pretty obvious.
>>
>> Berkeley DB databases can always be upgraded from older BDB versions with
>> db_upgrade, if the BDB version on the new server is incompatible with the
>> one on the old server. Nothing else should really matter.
> This is not necessarily reliable. I've encountered at least 4 BDB
> environments that worked as they were, but for which 'db_upgrade' was
> impossible. It even paid serious consulting rates while I backported a
> bunch of CentOS tools to work with an old BDB environment that someone
> had hand built and not written a usable 'export' function for.
>
> I have never found BDB to be stable or reliable enough for production use.

That's an answer to a different question. :)

>> We do still support all BDB repositories. We did not deprecate the BDB
>> backend because it would be inherently worse than FSFS, but because we
>> simply do not have the resources to adequately maintain and improve two (and
>> soon, three) repository back-ends. That's all.
> Do you intend to discard it in a foreseeable release? While it's been
> useful to take old SVN environments and be able to run 'svnadmin
> download' on them with newer Subversion releases, I'm not sure if it's
> worth just abandoning at some point. Does anyone use it by choice
> anymore?

http://subversion.apache.org/docs/release-notes/1.8.html#bdb-deprecated

I can't predict anything more than what we wrote in the release notes.
If we do decide to completely remove BDB support, we will definitely
tell our users a couple releases in advance, to give them enough time to
migrate.

-- Brane


-- 
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane@wandisco.com