From owner-freebsd-isp Wed Feb 25 21:12:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18015 for freebsd-isp-outgoing; Wed, 25 Feb 1998 21:12:08 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from asa1.asan.com (asa1.asan.com [206.20.111.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA17953 for ; Wed, 25 Feb 1998 21:12:01 -0800 (PST) (envelope-from bugtraq@asan.com) Received: from ppp147-1.asan.com (ppp147-1.asan.com [206.20.111.147]) by asa1.asan.com (NTMail 3.03.0016/1.aehb) with ESMTP id ta686861 for ; Thu, 26 Feb 1998 00:11:43 -0500 Message-Id: <3.0.3.32.19980226001042.0350fee0@asan.com> X-Sender: bugtraq@asan.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 26 Feb 1998 00:10:42 -0500 To: freebsd-isp@FreeBSD.ORG From: WaiKin Wong Subject: Re: BSD crashes under load In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 10:04 AM 2/25/98 -0800, you wrote: >The problem seems to be disk related. There is no panic message in the >log (or any message, for that matter); the machines simply spontaneously >reboot, fail the filesystem check, and drop into single-user mode. At >this point, running fsck brings up a long list of duplicate inodes/files >in the /usr slice. I would initially consider this to be problem with the >drive; however, replacing the drive on one server didn't fix it, and >another machine that was just added a week ago is starting to display this >behavior as well. This sort of thing should not be happening on a >brand-new drive. It might be a faulty motherboard. I had all of the following symptoms reported. It appeared to be disk related because the problems were more likely to be asserted by drive activity. Heat also caused problems by increasing likelyhood of reboots occuring. I've read that some motherboard manufacturers built boards that use capacitors and other components that can degrade over time. This may be why our machine functioned perfectly fine for months. And, even a motherboard swap caused continual problems. We eventually switched to a new board made by ASUS. The problems have stopped completely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message