From owner-freebsd-current  Sun Oct 13 17:43:12 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id RAA14481
          for current-outgoing; Sun, 13 Oct 1996 17:43:12 -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 RAA14475
          for <current@freebsd.org>; Sun, 13 Oct 1996 17:43:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id RAA07619; Sun, 13 Oct 1996 17:42:48 -0700 (PDT)
Message-Id: <199610140042.RAA07619@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: Karl Denninger <karl@Mcs.Net>
cc: current@freebsd.org
Subject: Re: More on the disappearing directory problem 
In-reply-to: Your message of "Sun, 13 Oct 1996 17:29:07 CDT."
             <199610132229.RAA01131@Jupiter.Mcs.Net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sun, 13 Oct 1996 17:42:48 -0700
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Errno = 2, which is "ENOENT", or the directory DISAPPEARED!  (This is being
>returned by the "getcwd" system call)
>
>However, if you then do an "ls -la", you DO see the directory and its
>contents.
>
>This is the only remaining open problem in the -CURRENT tree that we have.
>
>Anyone have any ideas on this?

   Just a thought... Look at the permissions of the underlying mount point for
the NFS directory and make sure that it doesn't restrict any access. I recall
that there was some sort of bug with NFS that the wrong inode is looked at
sometimes at the mount point.

-DG

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