From owner-freebsd-hackers Sun Nov 12 18:25:32 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA27817 for hackers-outgoing; Sun, 12 Nov 1995 18:25:32 -0800 Received: from shell.monmouth.com (pechter@shell.monmouth.com [205.164.220.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA27806 for ; Sun, 12 Nov 1995 18:25:27 -0800 Received: (from pechter@localhost) by shell.monmouth.com (8.6.12/8.6.12) id VAA21007; Sun, 12 Nov 1995 21:23:47 -0500 From: Bill/Carolyn Pechter Message-Id: <199511130223.VAA21007@shell.monmouth.com> Subject: Re: Odd crash after inode depletion.. To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Sun, 12 Nov 1995 21:23:46 -0500 (EST) Cc: FreeBSD-hackers@freebsd.org (FreeBSD-hackers) In-Reply-To: <199511120740.BAA26010@brasil.moneng.mei.com> from "Joe Greco" at Nov 12, 95 01:40:28 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 895 Sender: owner-hackers@freebsd.org Precedence: bulk > I've noticed an infrequent but consistent tendency for the system to panic > with "free vnode isn't" some time after hitting inode exhaustion. With a > sample size of only a few instances, all I can establish is that I have NOT > seen a "free vnode isn't" panic without first having run out of inodes. > > (system is running 1026-SNAP, by the way, which may be significant - I never > saw this panic under 2.0.5R, but then again, I can't recall ever having run > out of inodes under 2.0.5R) > > ... Joe > I'm seeing this as well without running out of Inodes... Bill ------------------------------------------------------------------------------- Bill Pechter/Carolyn Pechter | The postmaster always pings twice. Lakewood MicroSystems | 17 Meredith Drive, 908-389-3592 | Tinton Falls, NJ 07724 pechter@shell.monmouth.com |