From owner-freebsd-hackers  Fri Feb  6 18:29:50 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA18231
          for hackers-outgoing; Fri, 6 Feb 1998 18:29:50 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA18221
          for <hackers@FreeBSD.ORG>; Fri, 6 Feb 1998 18:29:41 -0800 (PST)
          (envelope-from evanc@synapse.net)
Received: (qmail 5264 invoked from network); 7 Feb 1998 02:29:36 -0000
Received: from cello.synapse.net (HELO cello) (199.84.54.81)
  by conductor.synapse.net with SMTP; 7 Feb 1998 02:29:36 -0000
Message-ID: <02b601bd3370$386d8fe0$2844c00a@cello.synapse.net>
From: "Evan Champion" <evanc@synapse.net>
To: "Robert Watson" <robert+freebsd@cyrus.watson.org>
Cc: "FreeBSD Hackers" <hackers@FreeBSD.ORG>
Subject: Re: More NFS Problems
Date: Fri, 6 Feb 1998 21:29:30 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe hackers"

>I have seen this behavior on a number of our -stable clients.  The clients
>hang trying to access the file system even after the server comes back up
>again.  The machine eventually has to be rebooted.  So much for a
>stateless system :).  As a result, we are very cautious about rebooting
>our file server during active client usage.  I haven't had this particular
>problem on our -current machines, but they are a little flaky anyway so
>who knows :).


I am always able to recover the system without rebooting by killing the
offending processes and restarting them.  However, each of my systems does
not run a large number of different tasks, so it is relatively easy to guess
what to kill on each system.  On a larger system, it might be just a lot
easier to restart.

Irrespective, I don't think it should be doing that :-)

Evan