From owner-freebsd-questions Tue Apr 7 16:03:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13681 for freebsd-questions-outgoing; Tue, 7 Apr 1998 16:03:38 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from iconmail.bellatlantic.net (iconmail.bellatlantic.net [199.173.162.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13629 for ; Tue, 7 Apr 1998 16:02:11 -0700 (PDT) (envelope-from dmm125@bellatlantic.net) Received: from myname.my.domain (client201-122-72.bellatlantic.net [151.201.122.72]) by iconmail.bellatlantic.net (IConNet Sendmail) with SMTP id SAA07080 for ; Tue, 7 Apr 1998 18:59:28 -0400 (EDT) Newsgroups: comp.unix.bsd.freebsd.misc Date: Tue, 7 Apr 1998 18:59:30 +0000 (GMT) From: Donn Miller X-Sender: dmm125@myname.my.domain To: questions@FreeBSD.ORG Subject: crc errors in tar files Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently was unpacking the full FreeBSD source distribution in single-user mode (with install.sh all), and I noticed that I got a crc error in the sys dist. But when I tried to upack the sys distribution by itself, the gzip errors went away. I repeated this a couple of more times with no errors. I had everything mounted async. I wonder if this is a meta-data problem that occasionally occurs on filesystems mounted async. Again, this error occured on a tarball, but then went away on the next try. I didn't modify the file in any way. Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message