From owner-freebsd-bugs Mon Apr 6 23:51:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06434 for freebsd-bugs-outgoing; Mon, 6 Apr 1998 23:51:47 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from csvax.cs.caltech.edu (csvax.cs.caltech.edu [131.215.131.131]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA06429 for ; Mon, 6 Apr 1998 23:51:45 -0700 (PDT) (envelope-from mika@varese.cs.caltech.edu) Received: from varese.cs.caltech.edu by csvax.cs.caltech.edu (4.1/1.34.1) id AA07648; Mon, 6 Apr 98 23:51:43 PDT Received: from localhost.cs.caltech.edu (localhost.cs.caltech.edu [127.0.0.1]) by varese.cs.caltech.edu (8.8.7/8.7.3) with SMTP id XAA27474; Mon, 6 Apr 1998 23:51:38 -0700 (PDT) Message-Id: <199804070651.XAA27474@varese.cs.caltech.edu> X-Authentication-Warning: varese.cs.caltech.edu: localhost.cs.caltech.edu [127.0.0.1] didn't use HELO protocol To: Poul-Henning Kamp Cc: jkh@time.cdrom.com, freebsd-bugs@FreeBSD.ORG Subject: Re: kern/6189 In-Reply-To: Your message of "Tue, 07 Apr 1998 08:26:59 +0200." <12200.891930419@critter.freebsd.dk> Date: Mon, 06 Apr 1998 23:51:38 -0700 From: Mika Nystrom Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'd love to see this reply too.. :) What I am seeing now is that for six seconds (as far as I can tell no more nor less) after an automounted filesystem has been umounted, the kernel does not realize that it is in fact possible to try again through amd, but instead returns a "file not found" error (I suppose the symlink(?) is being cached so that the reference to the actual mountpoint does indeed result in a file not found even though amd could be coaxed to remount the filesystem.) The reason I'm not sure if this is a bug or not is that perhaps any reference that would cause the kernel to cache this information might also keep amd from umounting.. perhaps someone else can shed some light on this? (Or is this what your elusive email was about?) Mika Poul-Henning Kamp writes: > >No there isn't. My first reply to this one was lost (somebody needs >to check out why this happens all time). I don't belive there is >a cache-bug. > >Poul-Henning > >In message <12533.891930176@time.cdrom.com>, "Jordan K. Hubbard" writes: >>Uh, he just told me in another email that there was a VFS cache problem >>_also_, independently of this one? >> >>> Synopsis: VFS cache confuses the kernel when using amd (VFS cache is broken >>) >>> >>> State-Changed-From-To: open-closed >>> State-Changed-By: phk >>> State-Changed-When: Mon Apr 6 23:12:35 PDT 1998 >>> State-Changed-Why: >>> see pr 6231 for the sequel. >>> >>> To Unsubscribe: send mail to majordomo@FreeBSD.org >>> with "unsubscribe freebsd-bugs" in the body of the message >> >> > >-- >Poul-Henning Kamp FreeBSD coreteam member >phk@FreeBSD.ORG "Real hackers run -current on their laptop." >"Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message