From owner-freebsd-questions@FreeBSD.ORG Fri May 15 14:24:15 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B492216A for ; Fri, 15 May 2015 14:24:15 +0000 (UTC) Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 78DD61299 for ; Fri, 15 May 2015 14:24:15 +0000 (UTC) Received: by igbyr2 with SMTP id yr2so221714457igb.0 for ; Fri, 15 May 2015 07:24:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GUSud2ANKTgByhlfpay4vdB8IPRDAVdt4kIi7/7aHxI=; b=HBgH9MJNWdLp/U8DQkJnuhs0H2MTA0Xrlo4W/nRgusOWnQgDNuhTWT561Amiy5wsRm UyTx4WSVvuKD9RiQ5eDfbgrOTOWgpGqdyoz2ktUFDDTUfJpR86VbKYSRqednbTvgoreU +Ox1foI/k8ghArho7lpuIWWuhEeOC1qD8WcwunhkmCWJoNeCcLRod7CD5bY2cVL8BD/5 /POIlBInsPB3VexjffOWOqylTip0pf6QgkoYw+Fnv0R/+kkrSWIiikWkklgDyd9unhsK m6uUTaQCJY/cYdRBRP3SJbHbMi9HxpxuG8QL4LU9F4IDNpf5eiloQeCmMdkZ7EvHyGTH 02BQ== MIME-Version: 1.0 X-Received: by 10.50.36.2 with SMTP id m2mr5278107igj.15.1431699854859; Fri, 15 May 2015 07:24:14 -0700 (PDT) Received: by 10.64.236.10 with HTTP; Fri, 15 May 2015 07:24:14 -0700 (PDT) In-Reply-To: References: <20150515013141.GB78765@ozzmosis.com> Date: Fri, 15 May 2015 22:24:14 +0800 Message-ID: Subject: Re: portsnap fetch : "snapshot is corrupt" From: Ben Woods To: Avinash Sonawane Cc: andrew clarke , "freebsd-questions@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 May 2015 14:24:15 -0000 On Friday, May 15, 2015, Avinash Sonawane wrote: > On Fri, May 15, 2015 at 7:01 AM, andrew clarke > wrote: > > On Thu 2015-05-14 20:13:53 UTC+0530, Avinash Sonawane (rootkea@gmail.com > ) > > I've noticed this happen in the past on the odd occasion. I ruled out > > hardware error on my machine and put it down to some sort of > > corruption (or more likely syncronisation problem) with the snapshot > > server(s). If I waited a while (a few hours) then re-ran portsnap the > > errors went away. > > Same here. Now I can fetch the portsnap without any "sync" errors. > > But from browsing the web and from the mailing list archives I found > this same problem to be quite frequent and having the only apparent > solution "just to wait few hours" > > Is this specific issue is bound to happen? I mean it seems as if > community has adjusted with it. Is this "sync" issue is inherent in > portsnap design? > I think this issue is to do with people trying to download the new portsnap files whilst the mirrors are still synchronizing. So perhaps it is not a flaw of portsnap itself, but that the mirrors don't flag that a synch is in progress and don't continue to use the old files until the synch is fully complete. I use subversion for synchronizing my ports tree, so I don't have this issue. Regards, Ben -- -- From: Benjamin Woods woodsb02@gmail.com