[jira] [Comment Edited] (SVN-4668) svnserve dump format order has changed

["Luke Perkins (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SVN-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15809512#comment-15809512 ] 

Luke Perkins edited comment on SVN-4668 at 1/8/17 3:00 PM:
-----------------------------------------------------------

I have one SVN repository that has been active since January of 2006. The database has been upgraded several times from 1.2, 1.4, 1.6 and 1.8 formats; however, the dump files have always been faithful between repository versions. The last time I ran comprehensive SVN dump checks was in November of 2016 without issue. One of the Ubuntu apt-get upgrades changed something that impacted the svnserve dump format.

Most other tools that I use have a compatibility switch to adjust for format changes. I strongly suggest that a compatibility switch be added. 

Another suggestion is an SVN utility that parses an SVN dump file and provides a Pass/Fail indication that the dump file is intact and has not been corrupted. Another tool is required that performs an SVN dump file to SVN dump file compare and assures that the repository database matches the SVN dump file.

The whole reason for SVN's existence is to assure accurate version control. I tend to be a paranoid administrator of 3 different SVN machines. The users of these SVN machines want me to assure that nothing has been corrupted in our archives.


was (Author: lukeperkins):
I have one SVN repository that has been active since January of 2006. The database has been upgraded several times from 1.2, 1.4, 1.6 and 1.8 formats; however, the dump files have always been faithful between repository versions. The last time I ran comprehensive SVN dump checks was in November of 2016 without issue. One of the Ubuntu apt-get upgrades changed something that impacted the svnserve dump format.

Most other tools that I use have a compatibility switch to adjust for format changes. I strongly suggest that a compatibility switch be added. 

Another suggestion is an SVN utility that parses an SVN dump file and provides a Pass/Fail indication that the dump file is intact and has not been corrupted. Another tool is required that performs an SVN dump file to SVN dump file compare and assures that the repository database matches the SVN dump file.

The whole reason for SVN's existence is to assure accurate version control. I tend to be a paranoid administrator of 3 different SVN machines. The users of these SVN machines what me to assure that nothing has been corrupted in our archives.

> svnserve dump format order has changed
> --------------------------------------
>
>                 Key: SVN-4668
>                 URL: https://issues.apache.org/jira/browse/SVN-4668
>             Project: Subversion
>          Issue Type: Bug
>          Components: svnserve
>    Affects Versions: 1.9.3
>         Environment:  Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-53-generic x86_64)
>            Reporter: Luke Perkins
>            Priority: Critical
>         Attachments: SvnserveDumpIssue_20170107.jpg
>
>
> The format of the svnserve dump file has changed somewhere between version 1.8 and 1.9.3 ( version 1.9.3 (r1718519)). I routinely perform svnserve dump operations of my repositories and compare them against archived copies of dump files to be used for emergency recovery operations.
> It appears the content order difference is benign other than "diff" operations fail. I have file illustrating the difference.
> The version information for svnserve dump is:
> svnserve, version 1.9.3 (r1718519)
>    compiled Mar 14 2016, 07:39:01 on x86_64-pc-linux-gnu
> Copyright (C) 2015 The Apache Software Foundation.
> This software consists of contributions made by many people;
> see the NOTICE file for more information.
> Subversion is open source software, see http://subversion.apache.org/
> The following repository back-end (FS) modules are available:
> * fs_fs : Module for working with a plain file (FSFS) repository.
> * fs_x : Module for working with an experimental (FSX) repository.
> * fs_base : Module for working with a Berkeley DB repository.
> Cyrus SASL authentication is available.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)