From hsu@katiska.clinet.fi  Fri May 15 23:09:13 1998
Received: from lohi.clinet.fi (UNKNOWN@lohi.clinet.fi [194.100.0.7])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06322
          for <FreeBSD-gnats-submit@freebsd.org>; Fri, 15 May 1998 23:09:12 -0700 (PDT)
          (envelope-from hsu@katiska.clinet.fi)
Received: from katiska.clinet.fi (katiska.clinet.fi [194.100.0.4])
	by lohi.clinet.fi (8.8.8/8.8.6) with ESMTP id JAA07367
	for <FreeBSD-gnats-submit@freebsd.org>; Sat, 16 May 1998 09:09:15 +0300 (EEST)
Received: (from root@localhost)
	by katiska.clinet.fi (8.8.8/8.8.6) id JAA26766;
	Sat, 16 May 1998 09:08:53 +0300 (EEST)
Message-Id: <199805160608.JAA26766@katiska.clinet.fi>
Date: Sat, 16 May 1998 09:08:53 +0300 (EEST)
From: Heikki Suonsivu <hsu@clinet.fi>
Reply-To: hsu@clinet.fi
To: FreeBSD-gnats-submit@freebsd.org
Subject: Possible NFS deadlock clue
X-Send-Pr-Version: 3.2

>Number:         6651
>Category:       kern
>Synopsis:       Possible NFS deadlock clue
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    peter
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri May 15 23:10:00 PDT 1998
>Closed-Date:    Sat Jan 19 15:01:03 PST 2002
>Last-Modified:  Sat Jan 19 15:01:36 PST 2002
>Originator:     Heikki Suonsivu
>Release:        FreeBSD 2.2.6-STABLE i386
>Organization:
Clinet, Espoo, Finland
>Environment:

NFS disks mounted back and forth.  Probably any -STABLE.

>Description:

NFS tends to cause computers to deadlock, ie. responds to ping, often
serves NFS requests (if an NFS server, not necessary), on console pressing
return to login prompt gives you a new line but no "password:" query.  We
have had problems with servers deadlocking for ages, but this might be a
clue, as I think I found a way repeat the problem.

>How-To-Repeat:

Take NFS client A and NFS server B.  Have systems up and do some access
from A to B, and while doing that, add

ipfw add xxx deny log udp from A to B 2049

ie. deny all NFS traffic, but leave other NFS related ports open.  Wait for
a minute or so, then remove the ipfw rule.  Now NFS client should awake,
more or less in limited time.  Instead, the hole client gets completely
deadlocked, no new processes get started etcetc.

I do not think this happens if all NFS services are closed simultaneously,
so closing nfsd port 2049 and leaving other servives open might have
something to do with this.

I'm not sure about time delay required to produce the problem, it could be
that it could be short.  If this was also the cause of the other deadlocks,
it might be that certain sequence of packets lost because of overload would
wake this up, and that would explain occasional deadlocks.  Incidentally
the deadlocks became rarer when we went to 100 Mbps switched network.

If you can't reproduce this, add the ipfw rule to client instead of the
server and retry. 

>Fix:
	
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->peter 
Responsible-Changed-By: phk 
Responsible-Changed-When: Sun May 17 23:04:06 PDT 1998 
Responsible-Changed-Why:  
Our Deputy NFS meister is Peter :-) 
State-Changed-From-To: open->feedback 
State-Changed-By: iedowse 
State-Changed-When: Sat Jan 19 14:06:08 PST 2002 
State-Changed-Why:  

Does this problem still occur with a recent 4.X-stable? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=6651 
State-Changed-From-To: feedback->closed 
State-Changed-By: iedowse 
State-Changed-When: Sat Jan 19 15:01:03 PST 2002 
State-Changed-Why:  

Mail to submitter bounces. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=6651 
>Unformatted:
