From owner-freebsd-questions  Wed Oct 16 14:21:15 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA06952
          for questions-outgoing; Wed, 16 Oct 1996 14:21:15 -0700 (PDT)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA06941
          for <freebsd-questions@freebsd.org>; Wed, 16 Oct 1996 14:21:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id OAA09664; Wed, 16 Oct 1996 14:22:24 -0700 (PDT)
Message-Id: <199610162122.OAA09664@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: brian@mediacity.com
cc: freebsd-questions@freebsd.org
Subject: Re: NFS stale handle on 2.1.5 
In-reply-to: Your message of "Wed, 16 Oct 1996 13:52:30 PDT."
             <19961016205230.21241.qmail@mediacity.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Wed, 16 Oct 1996 14:22:24 -0700
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>If server reboots, I end up with the following
>message on client:
>
>mount: /usx: Stale NFS file handle

   The ESTALE error is returned by the server whenever the mountpoint
filehandle is no longer valid. This can happen for a number of reason:

1) The filesystem mount hierarchy changed on the server.
2) The filesystem was dismounted and re-mounted again on the server.
3) The filesystem type wasn't the same as was originally mounted.
4) Perhaps other reasons I've forgotten.

>How does one get the NFS subsystem to recover correctly
>when the server reboots?

   I think the only remedy may be to do a forced dismount (umount -f). If this
doesn't work then that's a bug and should be fixed.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project