From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 21:45:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 0587D16A4DD for ; Wed, 5 Jul 2006 21:45:40 +0000 (UTC) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92AD943D45 for ; Wed, 5 Jul 2006 21:45:38 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (localhost.natserv.net [127.0.0.1]) by zoraida.natserv.net (Postfix) with ESMTP id 51C03B833; Wed, 5 Jul 2006 17:45:36 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on zoraida.natserv.net X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.1.3 Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id 0D6FBB822; Wed, 5 Jul 2006 17:45:36 -0400 (EDT) References: <20060704092127.GA55167@lpthe.jussieu.fr> <44AABBD9.4000603@samsco.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: Scott Long Date: Wed, 05 Jul 2006 17:45:35 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org, Michel Talon Subject: Re: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 21:45:40 -0000 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.