From owner-freebsd-current Wed Feb 26 12:52:17 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA02401 for current-outgoing; Wed, 26 Feb 1997 12:52:17 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA02321 for ; Wed, 26 Feb 1997 12:52:00 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA28674; Wed, 26 Feb 1997 13:48:47 -0700 From: Terry Lambert Message-Id: <199702262048.NAA28674@phaeton.artisoft.com> Subject: Re: some recent panics To: rjk@grauel.com (Richard J Kuhns) Date: Wed, 26 Feb 1997 13:48:46 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: <199702261904.OAA15353@watson.grauel.com> from "Richard J Kuhns" at Feb 26, 97 02:04:31 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The most recent (as of about 1000 EST 2/26/97) kernel seems to be extremely > fragile; it takes very little disk activity on my ASUS P5-120/64 MB RAM to > cause a panic (4 in the past 2 hours). I know -current is dangerous to run > and being worked on, and I'm not complaining, I'm just sending this on the > chance it may be useful to someone... Disable the directory name cases... there is a single agregate constant you can use to do this. I suspect it's a problem in the treatment of negative cache entries; the negative cache code was patched as a workaround for the rename and create cases in the FreeBSD code, and the Lite2 integration seems to have backed it out. Disable it by changing the '1' to '0' in the line: static int doingcache = 1; /* 1 => enable the cache */ In the file /sys/kern/vfs_cache.c. If you are compiled debug, and the sysctl has been merged back in, then you can toggle this at runtime after the kernel is up. I still suggest you turn it off by default, if you toggle it via debug, since I don't know if this bites you on boot or will bite you before you can run the sysctl. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.