From owner-freebsd-current  Thu Apr 10 10:38:58 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id KAA19655
          for current-outgoing; Thu, 10 Apr 1997 10:38:58 -0700 (PDT)
Received: from dopey.pathlink.com (dopey.pathlink.com [204.30.237.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA19609;
          Thu, 10 Apr 1997 10:38:26 -0700 (PDT)
Received: from dvl-1.pathlink.com (dvl-1.pathlink.com [204.30.237.241])
          by dopey.pathlink.com (8.8.5/8.8.4) with SMTP
	  id KAA25163; Thu, 10 Apr 1997 10:48:53 -0700 (PDT)
Message-Id: <199704101748.KAA25163@dopey.pathlink.com>
To: dyson@freebsd.org
Subject: Re: NFS/mmap freeze in 2.2R
Cc: freebsd-current@freebsd.org
From: kachun@zippo.com (Kachun Lee)
Date: Thu, 10 Apr 97 10:38:21 PST
X-Mailer: WinVN 0.99.8 (beta 2)
In-Reply-To: <5iism1$s6l@newsrv.zippo.com>
References: <199704100622.XAA19967@newport.ece.uci.edu> from Steven Wallace at "Apr 9, 97 11:22:15 pm" <5iism1$s6l@newsrv.zippo.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <5iism1$s6l@newsrv.zippo.com>, you say...
>
>> 
>> I have discovered how to freeze the system over an NFS mounted filesystem.
>> If you map a file over NFS read/write and shared, write
>> to the area in memory, and then have another program read that nfs file,
>> the system will freeze.  The freeze is kindof wierd though.
>> It appears that the kernel is still running somehow. 
>> I can change the sysconts vty's but typing and all other processes
>> are frozen and not running.
>> 
>Sounds like a recursive VFS locking problem or somesuch.  Thanks for the
>report, and will look at it ASAP.
>
>John

While you are at it, maybe, you want to check this out also. We noticed we have 
been getting these messages:

-------------
Apr  8 23:21:12 lois /kernel: vnode_pager_getpages: I/O read error
Apr  8 23:21:12 lois /kernel: vm_fault: pager input (probably hardware) error, 
P
ID 11987 failure
Apr  8 23:21:12 lois /kernel: pid 11987 (in.nnrpd), uid 7003: exited on signal 
11
--------------

since 2.2R or later with our NFS mounted news servers. They appeared at the NFS 
clients during news was expiring at the NFS server. That leaded me to believe 
that the message was triggered when someone was reading an article while the 
NFS server removed it - both systems kept running though.