Date: Wed, 5 Jul 2006 21:33:40 -0300 (ADT) From: User Freebsd <freebsd@hub.org> To: Francisco Reyes <lists@stringsutils.com> Cc: freebsd-stable@freebsd.org, Michel Talon <talon@lpthe.jussieu.fr> Subject: Re: NFS Locking Issue Message-ID: <20060705213223.U1171@ganymede.hub.org> In-Reply-To: <cone.1152135935.895287.72616.1000@zoraida.natserv.net> References: <20060704092127.GA55167@lpthe.jussieu.fr> <44AABBD9.4000603@samsco.org> <cone.1152135935.895287.72616.1000@zoraida.natserv.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Jul 2006, Francisco Reyes wrote: > Scott Long writes: > >> For what it's worth, I recently spent a lot of time putting FreeBSD 6.1 >> to the test as both an NFS client and server in a mixed OS environment. > > I have a few debugging settings/suggestions that have been sent my way and I > plan to try them tonight, but this is just another report.. > > FreeBSD only environment. > Today after hours going crazy with horrible performance I brought down nfsd > and brought it back up.. that simple process got vmstat 'b' column down and > everything was back to normal. > > Again this will not help anyone troubleshoot, but just to mention that it > happens even with a FreeBSD only environment. 'k, to those out there that know what is useful, and what isn't ... If Francisco had DDB enabled, did a CTL-ALT-ESC when the above happens, and does a 'panic' to crash the server and dump a core ... can anything useful be gleamed from that core dump? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060705213223.U1171>