On Mon, Jul 7, 2014 at 3:23 AM, Branko Čibej <brane_at_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.
> 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?
Received on 2014-07-07 12:48:54 CEST