From owner-freebsd-questions@FreeBSD.ORG Sat Aug 5 02:33:11 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69B6616A4DA for ; Sat, 5 Aug 2006 02:33:11 +0000 (UTC) (envelope-from gary@pattersonsoftware.com) Received: from mail-ihug.icp-qv1-irony2.iinet.net.au (ihug-mail.icp-qv1-irony2.iinet.net.au [203.59.1.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D88B43D45 for ; Sat, 5 Aug 2006 02:33:09 +0000 (GMT) (envelope-from gary@pattersonsoftware.com) Received: from 203-206-108-153.dyn.iinet.net.au (HELO tosh) ([203.206.108.153]) by mail-ihug.icp-qv1-irony2.iinet.net.au with ESMTP; 05 Aug 2006 10:33:07 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.07,214,1151856000"; d="scan'208"; a="579803669:sNHT21651368" From: "Gary Newcombe" To: Date: Sat, 5 Aug 2006 12:33:07 +1000 Message-ID: <000501c6b837$7d1ad3a0$1f01a8c0@tosh> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Aca4Nai3zK68EFUIQ3+rVzJJIhIX1QAAQjpg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 In-reply-to: <44D4008D.1000309@freebsd.org> X-Antivirus: avast! (VPS 0631-3, 04/08/2006), Outbound message X-Antivirus-Status: Clean Subject: RE: portsnap oddities X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Aug 2006 02:33:11 -0000 Sure, the /var slice is 2Gb and has plenty of room. [mesh:/home/gary]# portsnap --debug fetch Looking up portsnap.FreeBSD.org mirrors... 2 mirrors found. Fetching snapshot tag from portsnap1.FreeBSD.org... latest.ssl 100% of 256 B 512 kBps done. Fetching snapshot metadata... 6eb9d6e9f93dd6b8e2a88bdf9d394b7e77f75795f073a4100% of 299 B 650 kBps done. Updating from Thu 3 Aug 2006 04:45:32 EST to Sat 5 Aug 2006 11:06:54 EST. Fetching 0 metadata patches... done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 2 patches... /usr/libexec/phttpget portsnap1.FreeBSD.org bp/7c2d57a2388d4d5cd20e935c57727b5019fbdf06210ebf9b8f0b7c01bf072db5-ad06d1f7 b82db9ebcb496e7d48a754932622f1c8d6166564e61666d059f1b8fd bp/352d16ab1731729d4542c9c126034d6f27ce2830f297effb8831e6eb6a46cb31-ad3d5100 1a264245eab5894cece6c902d073841143e9ffc7ee8379948a44aae3 http://portsnap1.FreeBSD.org/bp/7c2d57a2388d4d5cd20e935c57727b5019fbdf06210e bf9b8f0b7c01bf072db5-ad06d1f7b82db9ebcb496e7d48a754932622f1c8d6166564e61666d 059f1b8fd: 200 OK http://portsnap1.FreeBSD.org/bp/352d16ab1731729d4542c9c126034d6f27ce2830f297 effb8831e6eb6a46cb31-ad3d51001a264245eab5894cece6c902d073841143e9ffc7ee83799 48a44aae3: 200 OK done. Applying patches... bspatch: Corrupt patch sha256: NEW: No such file or directory [: =: unexpected operator bspatch: Corrupt patch sha256: NEW: No such file or directory [: =: unexpected operator done. Fetching 2 new ports or files... /usr/libexec/phttpget portsnap1.FreeBSD.org f/ad06d1f7b82db9ebcb496e7d48a754932622f1c8d6166564e61666d059f1b8fd.gz f/ad3d51001a264245eab5894cece6c902d073841143e9ffc7ee8379948a44aae3.gz http://portsnap1.FreeBSD.org/f/ad06d1f7b82db9ebcb496e7d48a754932622f1c8d6166 564e61666d059f1b8fd.gz: 200 OK http://portsnap1.FreeBSD.org/f/ad3d51001a264245eab5894cece6c902d073841143e9f fc7ee8379948a44aae3.gz: 200 OK gunzip: stdin: not in gzip format snapshot is corrupt. Thanks Colin, Gary -----Original Message----- From: Colin Percival [mailto:cperciva@freebsd.org] Sent: Saturday, 5 August 2006 12:21 PM To: Gary Newcombe Cc: freebsd-questions@freebsd.org Subject: Re: portsnap oddities Gary Newcombe wrote: > I'm getting the following error when I use portsnap lately on one of my > servers: > [snip] > Fetching 2 new ports or files... > gunzip: stdin: not in gzip format > snapshot is corrupt. > > I have now removed /var/db/portsnap and started from scratch 3 times. This > fixes the problem, but a few days later, I get the same story. I haven't had > any problems on any of the other servers (although they have older kernels), > so I'm guessing this could be a problem with portsnap from this kernel build > or it's related to something else. First, the obvious thing to check: Are you running out of disk space on /var ? Second, please run 'portsnap --debug fetch' and send me the output; this will give me a chance of identifying the problem. Colin Percival