Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3965D200B28 for ; Sun, 26 Jun 2016 20:13:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 304CA160A5C; Sun, 26 Jun 2016 18:13:11 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9DF11160A38 for ; Sun, 26 Jun 2016 20:13:10 +0200 (CEST) Received: (qmail 82283 invoked by uid 500); 26 Jun 2016 18:13:09 -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 82273 invoked by uid 99); 26 Jun 2016 18:13:09 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Jun 2016 18:13:09 +0000 Received: from zulu.23.e-reka.si (89-233-126-4.dynamic.t-2.net [89.233.126.4]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id ECEC31A00A1 for ; Sun, 26 Jun 2016 18:13:08 +0000 (UTC) Subject: Re: Which is the best tool /process to migrate VSS (with history) to Subversion References: <167189a9-8191-c5e1-a2bf-3f956b783508@egosoft.com> <4b8403a0-f92a-44f8-0c14-6955c6ac1168@apache.org> To: "users@subversion.apache.org" From: =?UTF-8?Q?Branko_=c4=8cibej?= Organization: The Apache Software Foundation Message-ID: <9a61b419-8f5e-fc2e-6232-544f18545b1c@apache.org> Date: Sun, 26 Jun 2016 20:14:34 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit archived-at: Sun, 26 Jun 2016 18:13:11 -0000 On 26.06.2016 16:49, Mark Phippard wrote: > The issue is that a lot of VSS repositories have hidden corruptions > that do not surface until you try to migrate the history. It seems > like the corruptions are often in the history or something, so it is > only when you start trying to extract old data that it surfaces. The reason for that is that the architecture of VSS requires that every user has write access to the actual repository databases; these are just files in a shared folder, and VSS assumes that CIFS locking is sufficient to implement distributed transactions. Since that's not the case, there's no way to avoid silent corruptions. Back in the day I administered a VSS repository used by a team of some 20 or so developers ... fixing corruptions was a regular daily task. -- Brane