From owner-freebsd-stable@FreeBSD.ORG  Wed May 26 10:08:04 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1E5E4106566B
	for <freebsd-stable@freebsd.org>; Wed, 26 May 2010 10:08:04 +0000 (UTC)
	(envelope-from mark@islandnet.com)
Received: from mx21.islandnet.com (mx11.islandnet.com [199.175.107.100])
	by mx1.freebsd.org (Postfix) with ESMTP id 071E78FC1B
	for <freebsd-stable@freebsd.org>; Wed, 26 May 2010 10:08:03 +0000 (UTC)
Received: from [199.175.106.221] (port=36430 helo=helpdesk.islandnet.com)
	by mx1.islandnet.com with SMTP id 1OHDWt-000Dx0-41 ;
	Wed, 26 May 2010 03:08:03 -0700
From: Mark Morley <mark@islandnet.com>
To: Rick Macklem <rmacklem@uoguelph.ca>
Date: Wed, 26 May 2010 03:08:03 -0700
X-Priority: 3
X-Mailer: Islandnet.com Helpdesk Webmail
MIME-Version: 1.0
Message-Id: <20100526100804.1E5E4106566B@hub.freebsd.org>
Content-Type: text/plain; charset="UTF-8
Content-Transfer-Encoding: 8bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: freebsd-stable@freebsd.org, Mark Morley <mark@islandnet.com>
Subject: Re: NFS trouble on 7.3-STABLE i386
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 May 2010 10:08:04 -0000

On Tue, 25 May 2010 20:59:08 -0400 (EDT) Rick Macklem  wrote:
You could try this patch. (It reverts the only vnode locking change that I
can see was done the the nfs server between 7.1 and 7.3.):
--- nfs_serv.c.sav 2010-05-25 19:40:29.000000000 -0400
+++ nfs_serv.c 2010-05-25 19:41:38.000000000 -0400
@@ -3236,7 +3236,7 @@
   io.uio_rw = UIO_READ;
   io.uio_td = NULL;
   eofflag = 0;
- vn_lock(vp, LK_SHARED | LK_RETRY, td);
+ vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, td);
   if (cookies) {
    free((caddr_t)cookies, M_TEMP);
    cookies = NULL;
@@ -3518,7 +3518,7 @@
   io.uio_rw = UIO_READ;
   io.uio_td = NULL;
   eofflag = 0;
- vn_lock(vp, LK_SHARED | LK_RETRY, td);
+ vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, td);
   if (cookies) {
    free((caddr_t)cookies, M_TEMP);
    cookies = NULL;

If you get a chance to try it, please let us know if it helps, rick

Thanks, but unfortunately it didn't work.  Rebooted it four hours ago with the patch in place and at the moment I have seven nfsd processes stuck in that state.

Could it indicate a problem with the underlying disk system?  It's an aac0 raid, but it has no errors and the controller indicates all is well, so I doubt it.

Mark