From owner-freebsd-stable Tue Oct 22 5:27:28 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE91237B407 for ; Tue, 22 Oct 2002 05:27:27 -0700 (PDT) Received: from topperwein.dyndns.org (acs-24-154-51-184.zoominternet.net [24.154.51.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A4BC43E91 for ; Tue, 22 Oct 2002 05:27:26 -0700 (PDT) (envelope-from behanna@zbzoom.net) Received: from [192.168.168.10] ([192.168.168.10]) by topperwein.dyndns.org (8.12.6/8.12.5) with ESMTP id g9MCREbN000651 for ; Tue, 22 Oct 2002 08:27:14 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Tue, 22 Oct 2002 08:27:08 -0400 (EDT) From: Chris BeHanna Reply-To: Chris BeHanna To: FreeBSD-Stable Subject: Recent vnode-handling Changes? Message-ID: <20021022082423.F557-100000@topperwein.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Has there recently been some fundamental change in the way vnodes are invalidated or recycled? I've had a number of crashes lately, and most of them end up looking like invalid vnode pointers (I posted a recent such crashdump to this list a few days ago). Of course, I'm stressing that system much harder now: I'm doing video captures to a large RAID volume, and I'm working with file sizes in the 40-70GB regime, with a lot of I/O happening in a short amount of time. If this is a tuning issue, I'd be happy to try things suggested by those in the know. -- Chris BeHanna Software Engineer (Remove "bogus" before responding.) behanna@bogus.zbzoom.net Turning coffee into software since 1990. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message