From owner-freebsd-current  Sun Jun  1 22:26:50 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id WAA27819
          for current-outgoing; Sun, 1 Jun 1997 22:26:50 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA27814
          for <current@FreeBSD.ORG>; Sun, 1 Jun 1997 22:26:48 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id WAA02303; Sun, 1 Jun 1997 22:26:06 -0700 (PDT)
To: Bruce Evans <bde@zeta.org.au>
cc: current@FreeBSD.ORG
Subject: Re: processes hanging in getblk for shutdown on nfs client 
In-reply-to: Your message of "Mon, 02 Jun 1997 13:56:59 +1000."
             <199706020356.NAA08264@godzilla.zeta.org.au> 
Date: Sun, 01 Jun 1997 22:26:06 -0700
Message-ID: <2298.865229166@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I see this too, but also in RELENG_2_2; I haven't been able to simply
reboot either of my 2.2.2+ machines for some time now, being NFS
clients (which mutually mount one another using AMD).  They always
hang up trying to unmount the NFS volumes and force my application of
the old reset button.

					Jordan

> On my nfs client system with /usr nfs-mounted, a plain reboot command
> now always leaves sendmail and/or xntpd hanging on getblk.  The sync
> then fails because of dirty blocks.  There was no problem until a
> week or two ago.  There is no problem with the same kernel and similar
> utilities on my nfs server system.
> 
> Bruce