From owner-freebsd-hackers  Mon Nov 13 12:06:56 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id MAA24008
          for hackers-outgoing; Mon, 13 Nov 1995 12:06:56 -0800
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA23998
          for <hackers@FreeBSD.org>; Mon, 13 Nov 1995 12:06:53 -0800
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA17295; Mon, 13 Nov 1995 12:59:24 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199511131959.MAA17295@phaeton.artisoft.com>
Subject: Re: Odd crash after inode depletion..
To: jgreco@brasil.moneng.mei.com (Joe Greco)
Date: Mon, 13 Nov 1995 12:59:24 -0700 (MST)
Cc: jkh@time.cdrom.com, hackers@FreeBSD.org
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]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 846       
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)

This is endemic to the move from regualr to circular queues.  I don't know
why, but going back to the old queues fixes it.

Probably, this is just a symptom of the larger problem of global allocation
of vnodes.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.