From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 70186 invoked by alias); 20 Jul 2018 21:43:50 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 70176 invoked by uid 89); 20 Jul 2018 21:43:49 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=christmas, Christmas, raid, restoration X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 20 Jul 2018 21:43:48 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=SVR-IES-MBX-03.mgc.mentorg.com) by relay1.mentorg.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-SHA384:256) id 1fgdBh-0000C2-MX from joseph_myers@mentor.com ; Fri, 20 Jul 2018 14:43:45 -0700 Received: from digraph.polyomino.org.uk (137.202.0.87) by SVR-IES-MBX-03.mgc.mentorg.com (139.181.222.3) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 20 Jul 2018 22:43:42 +0100 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.86_2) (envelope-from ) id 1fgdBd-0000a0-IH; Fri, 20 Jul 2018 21:43:41 +0000 Date: Fri, 20 Jul 2018 21:48:00 -0000 From: Joseph Myers To: Alexandre Oliva CC: "Eric S. Raymond" , Bernd Schmidt , GCC Development , Subject: Re: Repo conversion troubles. In-Reply-To: Message-ID: References: <20180709191911.648443A4AA7@snark.thyrsus.com> <309363c2-0a5d-29f8-7c7e-19734e7cfa7a@t-online.de> <20180709195957.GB32057@thyrsus.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2018-07/txt/msg00315.txt.bz2 On Mon, 9 Jul 2018, Alexandre Oliva wrote: > On Jul 9, 2018, Jeff Law wrote: > > > On 07/09/2018 01:57 PM, Eric S. Raymond wrote: > >> Jeff Law : > >>> I'm not aware of any such merges, but any that occurred most likely > >>> happened after mid-April when the trunk was re-opened for development. > > >> I'm pretty certain things were still good at r256000. I've started that > >> check running. Not expecting results in less than twelve hours. > > > r256000 would be roughly Christmas 2017. > > When was the RAID/LVM disk corruption incident? Could it possibly have > left any of our svn repo metadata in a corrupted way that confuses > reposurgeon, and that leads to such huge differences? That was 14/15 Aug 2017, and all the SVN revision data up to r251080 were restored from backup within 24 hours or so. I found no signs of damage to revisions from the 24 hours or so between r251080 and the time of the corruption when I examined diffs for all those revisions by hand at that time. (If anyone rsynced corrupted old revisions from the repository during the window of corruption, those corrupted old revisions might remain in their rsynced repository copy because the restoration preserved file times and size, just fixing corrupted contents.) -- Joseph S. Myers joseph@codesourcery.com