From users-return-1355-daniel=haxx.se@subversion.apache.org Wed Mar 3 10:13:07 2010 Return-Path: Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by giant.haxx.se (8.14.3/8.14.3/Debian-9) with SMTP id o239D6vB012929 for ; Wed, 3 Mar 2010 10:13:07 +0100 Received: (qmail 40111 invoked by uid 500); 3 Mar 2010 09:13: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 40102 invoked by uid 99); 3 Mar 2010 09:13:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Mar 2010 09:13:01 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mdrozdziel@gmail.com designates 209.85.219.218 as permitted sender) Received: from [209.85.219.218] (HELO mail-ew0-f218.google.com) (209.85.219.218) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Mar 2010 09:12:55 +0000 Received: by ewy10 with SMTP id 10so859862ewy.36 for ; Wed, 03 Mar 2010 01:12:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=QehHjUX8Bz8cyGEi/tcpFZpMePJes3+CST5b1ptf4Wk=; b=gf43qzG7Vw3PNvoKu3M11IGKBdn4wLCpnEXzy7km2ltoxzYXv5reFmZZ6GEOZaAOgK WVGsMiM7SDBRGCVxAujzq0ozZbpWwJIUNKu/y3g9PILGBkmQCfs1RmkrpMfPqtYTrnxB sQe08dWt8aiaJvrLV9xHzZmI2T9ELd2YQRX/4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=t0mmH8uIP1U9t5LsDgyz4CzhnWoCZpw0M7mH0w7T5T+KYDihRZ2ZM8mI8yj6Vyg6Kp C3Zi4pKm9z/ZnU/sPAhfy5ZFCDj9QfuAvNJINYev5I8JAsN6R3L5l+FoenzVF7wExP9A E69ZAUoLw1xDmJr0KnVu0oK2hfAGGIYovU9hg= MIME-Version: 1.0 Received: by 10.213.80.1 with SMTP id r1mr1423458ebk.52.1267607553754; Wed, 03 Mar 2010 01:12:33 -0800 (PST) In-Reply-To: <29B06DD2A6115B4B991C0C6D091E78DA0243B99BB4@DEFTHW99E55MSX.ww902.siemens.net> References: <1c85be451003020609v6451f696ua2c3d02fcea0cdeb@mail.gmail.com> <29B06DD2A6115B4B991C0C6D091E78DA0243B99BB4@DEFTHW99E55MSX.ww902.siemens.net> Date: Wed, 3 Mar 2010 10:12:33 +0100 Message-ID: <1c85be451003030112p7f367915h7bc909882249ffb@mail.gmail.com> Subject: Re: Broken Revision in FSFS Repo From: =?UTF-8?Q?Mariusz_Dro=C5=BAdziel?= To: "Kutter, Martin" Cc: "users@subversion.apache.org" Content-Type: text/plain; charset=UTF-8 2010/3/2 Kutter, Martin : > This sounds a bit like our issue discussed in thread > "Corrupted FSFS commit" just a few days ago on this list. > We managed to create a copy of the repository without the corrupted > files using path-based authorization and svnsync. Could you give me some more insight on how exactly you performed the restore? I read up on your problem a bit, but theres no any details. Cloning my repo ends up the same way as everything does: Copied properties for revision 1024. Committed revision 1025. Copied properties for revision 1025. Committed revision 1026. Copied properties for revision 1026. Transmitting file data ............................................................................................... svnsync: Decompression of svndiff data failed > However, I'm a bit concerned about the issue arising again: Is there > some error in svn which allows for corrupted FSFS revisions to > enter into the repository? I read up a lot of problem-posts on the net, and theres a lot of people complaining about broken revs in their repo. Unfortunately the only solution which pops is the third party fsfsverify.py, which is failing in my case. I saw some posts about cases, when fsfsverify.py didn't worked, but usually there was no further information on if and how they managed to recover the data. Other solutions with dumping. cloning, skipping rev didn't worked, as I mentioned in the OP. My subversion version is 1.5.1. -- Mariusz Drozdziel