From owner-freebsd-stable@FreeBSD.ORG Wed Jun 28 08:18: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 38E7116A408 for ; Wed, 28 Jun 2006 08:18: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 4D0E743D98 for ; Wed, 28 Jun 2006 08:18:34 +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 52418B8A2 for ; Wed, 28 Jun 2006 04:18:33 -0400 (EDT) Received: from 35st-server.simplicato.com (static-71-249-233-130.nycmny.east.verizon.net [71.249.233.130]) by zoraida.natserv.net (Postfix) with ESMTP id E7439B89C for ; Wed, 28 Jun 2006 04:18:32 -0400 (EDT) Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: FreeBSD Stable List Date: Wed, 28 Jun 2006 04:18:32 -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 Subject: NFS clients freeze and can not disconnect 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, 28 Jun 2006 08:18:40 -0000 I have a series of machines 6.0 stable (various dates), 6.1 stable (various dates) that freeze if the NFS sever they are connected to becomes unresponsive or crashes. Was able to confirm this behavior for both i386 and AMD64. A 5.3 machine connected to the same nfs server was able to "umount -f" the volume. I was able to reproduce the problem in a test environment. Tried TCP, UDP connections, soft mount and a retry count of 1. It doesn't seem to matter whether the server is 6.X or 5.X (tested in both), it is the 6.X client that has the problem. Searching the archives seem to be a known issue. Is there a patch? Or has it recently being fixed? The dates of my 6.X client machines varies, but are 6.0 stable up to 6.1Stable may 29.