From owner-freebsd-current Thu Sep 6 22:24:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id DFF1037B403; Thu, 6 Sep 2001 22:24:50 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.4/8.11.4) with ESMTP id f875OHT86511; Fri, 7 Sep 2001 07:24:17 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "John W. De Boskey" Cc: Current List Subject: Re: __getcwd & errno 20 (Not a directory) vfs_cache.c In-Reply-To: Your message of "Thu, 06 Sep 2001 21:15:32 PDT." <20010906211532.A52687@FreeBSD.org> Date: Fri, 07 Sep 2001 07:24:17 +0200 Message-ID: <86509.999840257@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You are not supposed to call __getcwd() directly. Poul-Henning In message <20010906211532.A52687@FreeBSD.org>, "John W. De Boskey" writes: >Hi, > > I'm in the middle of trying to debug a java problem >and have found something I don't quite understand. > > Basically, __getcwd() is returning errno 20, Not >a directory. man getcwd doesn't list ENOTDIR so I >started looking in the sources and found kern/vfs_cache.c: > > if (vp->v_dd->v_id != vp->v_ddid) { > numcwdfail1++; > free(buf, M_TEMP); > return (ENOTDIR); > } > > > Could someone who is more familiar with the vfs >layers provide some pointers as to what is being >done here? The code is instrumented, and sysctl >has the following to say: > >% sysctl -a | grep cwd >vfs.cache.numcwdcalls: 225014 >vfs.cache.numcwdfail1: 845 1 -> ENOTDIR >vfs.cache.numcwdfail2: 6775 2 -> ENOENT >vfs.cache.numcwdfail3: 0 >vfs.cache.numcwdfail4: 0 >vfs.cache.numcwdfound: 217394 > > The really annoying aspect to this is that it doesn't >happen everytime, and happens more often when in a nfs >mounted directory vs. a local directory. > >Thanks! >John > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message