From mi@misha.cisco.com Mon Apr 26 07:40:23 1999
Return-Path: <mi@misha.cisco.com>
Received: from misha.cisco.com (misha.cisco.com [171.69.206.50])
	by hub.freebsd.org (Postfix) with ESMTP id 19704151FF
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 26 Apr 1999 07:40:21 -0700 (PDT)
	(envelope-from mi@misha.cisco.com)
Received: (from root@localhost)
	by misha.cisco.com (8.9.2/8.9.1) id KAA07685;
	Mon, 26 Apr 1999 10:40:20 -0400 (EDT)
	(envelope-from mi)
Message-Id: <199904261440.KAA07685@misha.cisco.com>
Date: Mon, 26 Apr 1999 10:40:20 -0400 (EDT)
From: Mikhail Teterin <mi@misha.cisco.com>
Reply-To: mi@aldan.algebra.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: find hangs in `nfsrcv' on local filesystem despite -xdev
X-Send-Pr-Version: 3.2

>Number:         11335
>Category:       bin
>Synopsis:       find hangs in `nfsrcv' on local filesystem despite -xdev
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Apr 26 07:50:01 PDT 1999
>Closed-Date:    Wed Sep 29 10:05:42 PDT 1999
>Last-Modified:  Wed Sep 29 10:07:22 PDT 1999
>Originator:     Mikhail Teterin
>Release:        FreeBSD 3.1-STABLE i386
>Organization:
Virtual Estates, Inc.
>Environment:

	The OS is: 3.1-STABLE as of Wed Mar 31 12:36:47 EST 1999

	Filesystems are as follows:

	/dev/wd0s2a on / (local, soft-updates, writes: sync 13 async 84747)
	/dev/wd0s1 on /c (NFS exported, local, read-only)
	/dev/wd0s4g on /tmp (local,
		soft-updates, writes: sync 189 async 34479)
	/dev/wd0s4h on /home (NFS exported, local,
		soft-updates, writes: sync 8837 async 299655)
	/dev/wd0s4f on /usr (NFS exported, local,
		soft-updates, writes: sync 1682 async 245762)
	/dev/wd0s4e on /var (NFS exported, local,
		soft-updates, writes: sync 5973 async 213023)
	procfs on /proc (local)
udp:	172.27.164.20:/exports on /exports (read-only)
udp:	172.27.164.20:/exports/FreeBSD-2.2.6 on /exports/FreeBSD-2.2.6 (read-only)
udp:	tornado:/var/mail on /var/mail (union)
udp:	ch-dtdhome:/ch-dtdhome5 on /users (union)
udp:	ch-dtdhome:/ch-dtdhome4 on /users (union)
udp:	ch-dtdhome:/ch-dtdhome3 on /users (union)
udp:	ch-dtdhome:/ch-dtdhome2 on /users (union)
udp:	ch-dtdhome:/ch-dtdhome1 on /users (union)
tcp:	rtfm:/home/mi on /rtfm
udp:	labserv:/usr/homes on /usr/homes (union)

>Description:

	A simple `find / -xdev -type f' hangs without a single line of
	output. `ps -axlww | grep pid' shows:
  105  7553 10201   0  -1  0   800  504 nfsrcv I     p4    0:00.01 / (find)

	The reason for making this "critical" and "high priority" is because
	the /etc/security script hangs on line 33 (find $mount -xdev...)

>How-To-Repeat:

	See description.

>Fix:
	
	Don't know...

>Release-Note:
>Audit-Trail:

From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
To: mi@aldan.algebra.com
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: bin/11335: find hangs in `nfsrcv' on local filesystem despite -xdev
Date: Mon, 26 Apr 1999 12:51:16 -0400 (EDT)

 <<On Mon, 26 Apr 1999 10:40:20 -0400 (EDT), Mikhail Teterin <mi@misha.cisco.com> said:
 
 >> Description:
 
 > 	A simple `find / -xdev -type f' hangs without a single line of
 > 	output. `ps -axlww | grep pid' shows:
 >   105  7553 10201   0  -1  0   800  504 nfsrcv I     p4    0:00.01 / (find)
 
 That's Just The Way It Is.  `find' has to stat the mount point in
 order to find out that it is in fact a mount point.
 
 -GAWollman
 
  
 

From: Mikhail Teterin <mi@misha.cisco.com>
To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman)
Cc:  
Subject: Re: bin/11335: find hangs in `nfsrcv' on local filesystem despite -xdev
Date: Mon, 26 Apr 1999 12:59:30 -0400 (EDT)

 Garrett Wollman once wrote:
 
 > <<On Mon, 26 Apr 1999 10:40:20 -0400 (EDT), Mikhail Teterin <mi@misha.cisco.com> said:
 > 
 > >> Description:
 > 
 > > 	A simple `find / -xdev -type f' hangs without a single line of
 > > 	output. `ps -axlww | grep pid' shows:
 > >   105  7553 10201   0  -1  0   800  504 nfsrcv I     p4    0:00.01 / (find)
 > 
 > That's Just The Way It Is.  `find' has to stat the mount point in
 > order to find out that it is in fact a mount point.
 
 And there is no other, safe, way to do it? At least, may be forking off
 a child, a'la AMD?
 
 Something has to be done about /etc/security then -- I come on Monday to
 see the Saturday and Sunday daily runs hanging...
 
 Yours,
 
 	-mi
 
 
State-Changed-From-To: open->closed 
State-Changed-By: dillon 
State-Changed-When: Wed Sep 29 10:05:42 PDT 1999 
State-Changed-Why:  
This bug is believed to be fixed in the 3.3 release as well as in -current. 
The bug that was fixed was a realignment bug related to NFS/TCP mounts, 
causing NFS/TCP mounts to hang indefinitely when subjected to heavy loads. 
>Unformatted:
