Date: Mon, 8 Jun 1998 14:41:41 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Terry Lambert <tlambert@primenet.com> Cc: current@FreeBSD.ORG Subject: Re: NFS / softupdates interaction problems? Message-ID: <199806081841.OAA07137@grasshopper.cs.duke.edu> In-Reply-To: <199806081832.LAA12771@usr04.primenet.com> References: <199806081336.JAA06735@grasshopper.cs.duke.edu> <199806081832.LAA12771@usr04.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806081841.OAA07137>