From owner-freebsd-current Mon Apr 1 08:44:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA05089 for current-outgoing; Mon, 1 Apr 1996 08:44:03 -0800 (PST) Received: from vector.jhs.local (slip139-92-42-129.ut.nl.ibm.net [139.92.42.129]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA04640 Mon, 1 Apr 1996 08:43:44 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by vector.jhs.local (8.7.3/8.6.9) with SMTP id KAA00437; Mon, 1 Apr 1996 10:59:40 +0200 (MET DST) Message-Id: <199604010859.KAA00437@vector.jhs.local> X-Authentication-Warning: vector.jhs.local: Host localhost [127.0.0.1] didn't use HELO protocol To: "Christoph P. Kukulies" cc: freebsd-current@freefall.FreeBSD.org Subject: Re: spurious problems with a P150 system From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 (pending modem change) Web: http://www.freebsd.org/~jhs/ Mailer: EXMH version 1.6.5 95 12 11, PGP available In-reply-to: Your message of "Fri, 29 Mar 1996 18:08:01 +0100." <199603291708.SAA24113@gilberto.physik.rwth-aachen.de> Date: Mon, 01 Apr 1996 10:59:40 +0200 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: "Christoph P. Kukulies" > Subject: Re: spurious problems with a P150 system > Date: Fri, 29 Mar 1996 18:08:01 +0100 > Message-id: <199603291708.SAA24113@gilberto.physik.rwth-aachen.de> > > Now and then it happens now that files are clobbered. How clobbered ? Zero sized or screwed data ? I have a current problem that was initially assumed software/OS rev/incompat. libs etc, but turns out to be a flaky disk: HP 97548S C023" type 0 fixed SCSI 1 Every so often 8 bytes in my files get zapped to 0xFF. Your err. condition is no doubt different to mine, but you might want to check your disc, so I'm privately mailing you a little program called testblock.c + man, simply use it to write than check one enormous file on the remaining space on that file system. Unix FSs dont generally have Cksums in, 'cos it would heavily impact the performance particularly when accessing large files. Normally disks supposedly have error recovery electronics, but if that fails .... Intriguingly I have 2 `identical' HP drives, & the bad one has an extra jumper on, without which the scsi bus hangs during boot, I rather suspect this is some kind of `over-ride the default hang-on-err-detect-in-cache-boot-check' strap, but I don't know 'cos I only have the `Product Description Manual' & not a factory/service manual. testblock.c should hopefully help nail down where your problem is, it's probably software, but if it unexpectedly is flaky hardware, testblock.c might catch it for you :-) Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/