From owner-freebsd-net@FreeBSD.ORG Thu Apr 7 20:20:35 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 088FA16A4CE for ; Thu, 7 Apr 2005 20:20:35 +0000 (GMT) Received: from mta1.lbl.gov (mta1.lbl.gov [128.3.41.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD3B443D3F for ; Thu, 7 Apr 2005 20:20:34 +0000 (GMT) (envelope-from dart@nersc.gov) Received: from mta1.lbl.gov (localhost [127.0.0.1]) by mta1.lbl.gov (8.12.10/8.12.10) with ESMTP id j37KKVn3003487 for ; Thu, 7 Apr 2005 13:20:32 -0700 (PDT) Received: from [127.0.0.1] (dhcp163-8.nersc.gov [128.55.8.163]) by mta1.lbl.gov (8.12.10/8.12.10) with ESMTP id j37KKVP9003478; Thu, 7 Apr 2005 13:20:31 -0700 (PDT) Message-ID: <4255960F.2010004@nersc.gov> Date: Thu, 07 Apr 2005 13:20:31 -0700 From: Eli Dart Organization: NERSC Center, LBNL User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Charles Swiger References: <42558F33.5090109@nersc.gov> In-Reply-To: X-Enigmail-Version: 0.90.1.1 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: Disable NFS client cache (or other traffic reduction methods) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dart@nersc.gov List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2005 20:20:35 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> Is there a way to disable client-side caching? I've looked, and >> can't seem to find one. Or, do I have this wrong and there is >> something else that is causing this? > > > Take a look through "man mount_nfs" for: > > -a Set the read-ahead count to the specified value. This may > be in > the range of 0 - 4, and determines how many blocks will be > read > ahead when a large file is being read sequentially. Trying a > value greater than 1 for this is suggested for mounts with a > large bandwidth * delay product. I did see this. Since the client is not reading any files (I think all the reads are being done by the NFS layer, not by any userland processes with open files) I had ignored -a. > > ...and the -o ac*** options. Although you may be right-- I was a bit > surprised not to see a "-o noac", myself. Solaris has one: Hmmmm.....any NFS gurus know whether setting the ac* options to 0 will disable client caching? Or, will setting these to 0 result in the client NFS layer fetching the data from the server and then immediately expiring it? Thanks, --eli > > noac Suppress data and attribute caching. > > :-) > - -- - ------------------------------------------------------------------- Eli Dart Office: (510) 495-2999 NERSC Center Networking and Security Group Cell: (510) 703-4508 Lawrence Berkeley National Laboratory Fax: (510) 486-4316 PGP Fingerprint = C970 F8D3 CFDD 8FFF 5486 343A 2D31 4478 5F82 B2B3 - ------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD4DBQFCVZYOLTFEeF+CsrMRAlReAKDMxrs97SSkZJRhaEVxRRpO51XrsACXX983 grAaYcgINLwiLtzoz3nLhQ== =GAZ7 -----END PGP SIGNATURE-----