From owner-freebsd-questions Mon Apr 20 14:06:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18626 for freebsd-questions-outgoing; Mon, 20 Apr 1998 14:06:10 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from mail.iconz.co.nz (mail.iconz.co.nz [202.14.100.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18456 for ; Mon, 20 Apr 1998 21:05:02 GMT (envelope-from jonc@pinnacle.co.nz) Received: from news.iconz.co.nz (status.gen.nz [202.14.100.1]) by mail.iconz.co.nz (8.8.7/8.8.7) with ESMTP id JAA056840893106276; Tue, 21 Apr 1998 09:04:36 +1200 (NZST) Received: (from uucp@localhost) by news.iconz.co.nz (8.8.5/8.8.5) with UUCP id JAA02269; Tue, 21 Apr 1998 09:07:28 +1200 Received: from tui.pinnacle.co.nz (tui.pinnacle.co.nz [202.37.163.3]) by kakapo.pinnacle.co.nz (8.8.8/8.8.8) with ESMTP id IAA02941; Tue, 21 Apr 1998 08:50:31 +1200 (NZST) Received: from localhost (jonc@localhost) by tui.pinnacle.co.nz (8.8.8/8.8.8) with SMTP id IAA18154; Tue, 21 Apr 1998 08:50:30 +1200 (NZST) X-Authentication-Warning: tui.pinnacle.co.nz: jonc owned process doing -bs Date: Tue, 21 Apr 1998 08:50:30 +1200 (NZST) From: Jonathan Chen To: "Randy A. Katz" cc: freebsd-questions@FreeBSD.ORG Subject: Re: cpio copies - file corruption??? In-Reply-To: <3.0.5.32.19980420085324.039ab150@ccsales.com> 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 On Mon, 20 Apr 1998, Randy A. Katz wrote: > Hello, > > I have just noticed that some text (and binary) files are being corrupted > when cpio copying. > > I have seen this on FreeBSD 2.1.0, 2.1.7, 2.2.5, and 2.2.6. > > I originally thought it was because I was copying through an NFS mount but > then I tried to copy from one partition to the next on a 2.2.6 machine and > got the same kind of results, various files having parts of other files and > junk in them... The last 2 times this happened to me it was due to: 1. bad memory. 2. bad drive (forcing an fsck would see heaps of errors even if the drive had been dismounted cleanly) It's usually some h/w problem. -- Jonathan Chen --------------------------------------------------------------------- When all other forms of communication fail, use words To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message