portsnap snapshot corruption?

Brooks Davis brooks at freebsd.org
Thu Sep 20 15:37:16 PDT 2007


On Thu, Sep 20, 2007 at 03:30:15PM -0700, Marcus Reid wrote:
> On Thu, Sep 20, 2007 at 09:46:06PM +0300, Giorgos Keramidas wrote:
> > On 2007-09-20 21:42, Giorgos Keramidas <keramida at FreeBSD.org> 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 at kobe:/root# rm -fr /var/db/portsnap/*
> > > % root at 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 at 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.

[5:32pm] brooks at coredump (/var/db): sudo portsnap fetch
Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found.
Fetching public key from portsnap2.FreeBSD.org... done.
Fetching snapshot tag from portsnap2.FreeBSD.org... done.
Fetching snapshot metadata... done.
Fetching snapshot generated at Wed Sep 19 20:07:10 CDT 2007:
1a2086f1a8eea72b21ecc5c6a03587a26e3b86055bc54a100% of   49 MB  366 kBps 00m00s
Extracting snapshot... done.
Verifying snapshot integrity... done.
Fetching snapshot tag from portsnap2.FreeBSD.org... done.
Fetching snapshot metadata... done.
Updating from Wed Sep 19 20:07:10 CDT 2007 to Thu Sep 20 16:06:41 CDT 2007.
Fetching 4 metadata patches... done.
Applying metadata patches... done.
Fetching 0 metadata files... done.
Fetching 42 patches.....10....20....30....40. done.
Applying patches... done.
Fetching 2 new ports or files... done.
[5:36pm] brooks at coredump (/var/db):

-- BRooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20070920/7e2ed3ee/attachment.pgp


More information about the freebsd-current mailing list