From owner-freebsd-questions@FreeBSD.ORG Wed Mar 2 23:55:38 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E751316A4CE for ; Wed, 2 Mar 2005 23:55:38 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D0B843D53 for ; Wed, 2 Mar 2005 23:55:36 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j22NtOBI077756; Wed, 2 Mar 2005 17:55:24 -0600 (CST) (envelope-from dan) Date: Wed, 2 Mar 2005 17:55:24 -0600 From: Dan Nelson To: Bob Johnson Message-ID: <20050302235524.GE77052@dan.emsphone.com> References: <42262EF2.8070503@eng.ufl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42262EF2.8070503@eng.ufl.edu> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.8i cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD NFS client and Netware 6.5 NFS server X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 23:55:39 -0000 In the last episode (Mar 02), Bob Johnson said: > Message below is about a FreeBSD server I maintain. The FreeBSD > server is our web server. We use NFS to talk to a Netware file > server where most of our users' web pages are stored. FreeBSD is > 5.3, and was working ok with Netware 5.1 (and still is with other > Netware servers). One of the servers was recently upgraded to > Netware 6.5 and NFS is no longer playing nice between the two. > > When something on the Netware side updates a file by copying it into > place (e.g. using FTP [don't complain] to upload a file), the FreeBSD > client doesn't find out that the file contents have changed until it > does something to the file (e.g. touch or chmod). Thus, when one of > our users updates their web page with something like Dreamweaver, the > web server doesn't find out about it (perhaps it eventually finds > out, but it takes more than the several minutes we waited). It sounds sort of like the vfs.nfs.access_cache_timeout sysctl isn't being honored on the FreeBSD side. The kernel defaults to 60 seconds, but if you have nfs_client_enable="YES" in rc.conf, /etc/rc.d/nfsclient sets it to 2. If you dump the NFS traffic as your web server fetches one of these recently-updated files, do you see it doing an ACCESS/GETATTR on the target files at all? -- Dan Nelson dnelson@allantgroup.com