From owner-freebsd-current Mon Jun 8 11:42:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15003 for freebsd-current-outgoing; Mon, 8 Jun 1998 11:42:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14846 for ; Mon, 8 Jun 1998 11:41:58 -0700 (PDT) (envelope-from gallatin@duke.cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.8.5/8.8.5) with ESMTP id OAA00025; Mon, 8 Jun 1998 14:41:41 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.8.8/8.8.8) id OAA07137; Mon, 8 Jun 1998 14:41:41 -0400 (EDT) (envelope-from gallatin) Date: Mon, 8 Jun 1998 14:41:41 -0400 (EDT) Message-Id: <199806081841.OAA07137@grasshopper.cs.duke.edu> From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: NFS / softupdates interaction problems? In-Reply-To: <199806081832.LAA12771@usr04.primenet.com> References: <199806081336.JAA06735@grasshopper.cs.duke.edu> <199806081832.LAA12771@usr04.primenet.com> X-Mailer: VM 6.31 under 20.2 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: > > I am unclear here, so I suspect others are as well. Does the crash still > occur regarless of your soft updates/vfs.nfs.async settings, or is the > crash cured by the same cases where the messages are cured? > > Ie: is the crash a soft updates problem or an general problem? Sorry.. that was a bit less than clear. The panic happens only with softupdates, and I've only seen it with vfs.nfs.async=1, but I've not run very much with vfs.nfs.async=0 (so as to avoid getting zillions of the above messages). In browsing the -current archive, I've seen this panic reported by Zach Heilig on 23 May (same stack trace), and Wm Brian McCane on June 3 (he only reported the panic string). So I'd assumed it was a known problem & just wanted to chime in with a "me too." Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message