From owner-freebsd-current@FreeBSD.ORG Thu Sep 20 22:30:16 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2054616A4D7 for ; Thu, 20 Sep 2007 22:30:16 +0000 (UTC) (envelope-from marcus@blazingdot.com) Received: from marklar.blazingdot.com (marklar.blazingdot.com [207.154.84.83]) by mx1.freebsd.org (Postfix) with SMTP id 09D7C13C44B for ; Thu, 20 Sep 2007 22:30:15 +0000 (UTC) (envelope-from marcus@blazingdot.com) Received: (qmail 93114 invoked by uid 503); 20 Sep 2007 22:30:15 -0000 Date: Thu, 20 Sep 2007 15:30:15 -0700 From: Marcus Reid To: Giorgos Keramidas Message-ID: <20070920223015.GA88368@blazingdot.com> References: <20070920184201.GA72805@kobe.laptop> <20070920184606.GA73060@kobe.laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070920184606.GA73060@kobe.laptop> X-Coffee-Level: nearly-fatal User-Agent: Mutt/1.5.6i Cc: freebsd-current@FreeBSD.org, Colin Percival Subject: Re: portsnap snapshot corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Sep 2007 22:30:16 -0000 On Thu, Sep 20, 2007 at 09:46:06PM +0300, Giorgos Keramidas wrote: > On 2007-09-20 21:42, Giorgos Keramidas wrote: > > Hi Colin, > > > > I've tried removing all of /var/db/portsnap/* and refetching several > > times today, but all the attempts resulted in corrupt snapshots, like > > this one: > > > > % root@kobe:/root# rm -fr /var/db/portsnap/* > > % root@kobe:/root# portsnap fetch > > % Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found. > > % Fetching public key from portsnap3.FreeBSD.org... done. > > % Fetching snapshot tag from portsnap3.FreeBSD.org... done. > > % Fetching snapshot metadata... done. > > % Fetching snapshot generated at Thu Sep 20 04:07:10 EEST 2007: > > % 1a2086f1a8eea72b21ecc5c6a03587a26e3b86055bc54a100% of 49 MB 1451 kBps 00m00s > > % Extracting snapshot... done. > > % Verifying snapshot integrity... gunzip: snap/2bafbd0d8edc7a7cfa7e19833986ae4032f82006fd0d65cba9c4a75b432b5c8e.gz: unexpected end of file > > % gunzip: snap/2bafbd0d8edc7a7cfa7e19833986ae4032f82006fd0d65cba9c4a75b432b5c8e.gz: uncompress failed > > % snapshot corrupt. > > % root@kobe:/root# > > > > Is something wrong with the portsnap servers, or should I try to see if > > there's something odd with my latest CURRENT upgrade? > > Damn, right after having spent an hour on this *and* posting a message, > our local admin notified us that our network has started using a > transparent proxy -- which is apparently broken. > > Sorry for the noise. I'll try to resolve this with our IT guys :) I've been having the same problem and I'm not behind any sort of proxy. Also, what sort of proxy would corrupt that 49MB gzipped tar file in a way that it passes gunzip -t? I think this is a real problem with the snapshots being served up by the portsnap servers. I posted this issue to freebsd-ports@ yesterday. Would someone please do an initial portsnap fetch and let me know if it works for them? I haven't seen a "works for me" yet since this problem started. Thank You, Marcus