Date: Thu, 09 Oct 1997 19:59:03 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Karl Denninger <karl@Mcs.Net> Cc: Robin Cutshaw <robin@intercore.com>, freebsd-current@FreeBSD.ORG Subject: Re: NFS cache problem in 3.0 SNAP Message-ID: <2907.876419943@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 09 Oct 1997 12:02:08 CDT." <19971009120208.12168@Mars.Mcs.Net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <19971009120208.12168@Mars.Mcs.Net>, Karl Denninger writes: >> >> I just upgraded to 3.0-971003-SNAP and have an NFS client problem. If >> I change a file on the NFS server (FreeBSD 2.2.1), the change does not >> show up on the 3.0 client > >This is a problem that I reported some time ago, and it remains open. > >Its actually quite a bit more serious than you might think; look for my >previous message in the archives for the exact behavior(s) that are >exhibited under different conditions. I backed my VOP_LOOKUP change out recently, I pressume that improved the situation a bit or hur ? I'm wondering if we need a call from the nfs code to the namecache when the nfs code decides that a directory has been changed. Anybody know where we can detect that situation ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2907.876419943>