From owner-freebsd-stable Thu Feb 11 18:24:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29174 for freebsd-stable-outgoing; Thu, 11 Feb 1999 18:24:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29154 for ; Thu, 11 Feb 1999 18:24:03 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id TAA05667; Thu, 11 Feb 1999 19:23:35 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199902120223.TAA05667@freeway.dcfinc.com> Subject: Re: panics with ufs_dirbad on high swapping. In-Reply-To: <19990211180841.50090@demos.su> from "Mikhail A. Sokolov" at "Feb 11, 99 06:08:41 pm" To: mishania@demos.net (Mikhail A. Sokolov) Date: Thu, 11 Feb 1999 19:23:35 -0700 (MST) Cc: stable@FreeBSD.ORG Reply-to: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Mikhail A. Sokolov wrote: > > given the 3.0-STABLE as of 1999-02-07, we experience the following > panics. The situation is the following - the box was rarely up for > more than 3-4 days since November (yes, I know there were fixes for > ufs_dirbad() then) and it happens way strange way. It will hang > (nothing but disk IO works, console doesn't respond, network > connections get staled and so on) when pretty big swap quantity is > being used actively (please find below the prepanic top results). > More the uptime gets, more longer perionds of irresponsibilities get, > and it would finally crash in 3 or 4 days with exactly the very same > panic. I already changed all the disks during this period, > reinstalled the / from 3.0-R -> 3.0-S on newly newfs'ed one and voila, > nothing helps. Since you're already willing to completely re-load the box, how about you load it with 2.2.8. Unless there are some features in 3.0 you can't live without, it'd be interesting if 2.2.8 (or 2.2-STABLE) made your problems go away. It would isolate the hardware/software question, and perhaps give you a stable system in the meantime. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message