From owner-freebsd-current@FreeBSD.ORG  Thu Aug 28 13:39:10 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 384EF16A4BF; Thu, 28 Aug 2003 13:39:10 -0700 (PDT)
Received: from h190n1fls34o809.telia.com (h190n1fls34o809.telia.com
	[213.67.96.190])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4AC4243FDD; Thu, 28 Aug 2003 13:39:08 -0700 (PDT)
	(envelope-from pawel.worach@telia.com)
Received: from telia.com (corona.sajd.net [192.168.1.20])
	h7SKd6f20418;	Thu, 28 Aug 2003 22:39:06 +0200 (MEST)
Message-ID: <3F4E6869.3060801@telia.com>
Date: Thu, 28 Aug 2003 22:39:05 +0200
From: Pawel Worach <pawel.worach@telia.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5b) Gecko/20030825
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Robert Watson <rwatson@freebsd.org>, current@freebsd.org
References: <Pine.NEB.3.96L.1030828084515.34202C-100000@fledge.watson.org>
	<3F4E39BF.10001@telia.com>
In-Reply-To: <3F4E39BF.10001@telia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: nfs tranfers hang in state getblck or nfsread
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Aug 2003 20:39:10 -0000

Pawel Worach wrote:
> Robert Watson wrote:
> 
>> On Wed, 27 Aug 2003, Pawel Worach wrote:
>>
>> Ok, so let me see if I have the sequence of events straight:
>>
> 
> Hope this is not as confusing as my previus mail :)
> 

Here is some more information.
I realized that i had tcp and udp "blackholing" enabled on the server so i
disabled that, still no dice.
disabled rpc.statd and rpc.lockd, still no dice.

I escaped to DDB between the "not responding" and the "ok" messages
and came up with this:
[SLP]nfscon <address>] mount_nfs
[SLP]- <address>] nfsiod 3
[SLP]- <address>] nfsiod 2
[SLP]- <address>] nfsiod 1
[SLP]- <address>] nfsiod 0

I have also played with the mount options, here is the result of that:
ro,nfsv3,tcp,rdirplus - broken
ro,nfsv3,tcp - broken
ro,tcp - broken
ro - ok (defaults to nfsv2,udp according to my research)
ro,nfsv3 - ok (defaults to udp)

So it looks like what i said before, only tcp seems to cause this.

As this is the first time i'm seriusly investigating this i also noted
that a restart of the NFS daemons (or reboot) of the server is not needed,
just doing a _clean_ reboot (init 6, shutdown -r now) of the client will
make the server "recover". (sometimes is takes two clean reboots).

	- Pawel