From owner-freebsd-questions@FreeBSD.ORG Sun Nov 20 07:50:53 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 606C116A41F for ; Sun, 20 Nov 2005 07:50:53 +0000 (GMT) (envelope-from mse_software@charter.net) Received: from mxsf20.cluster1.charter.net (mxsf20.cluster1.charter.net [209.225.28.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED61B43D45 for ; Sun, 20 Nov 2005 07:50:52 +0000 (GMT) (envelope-from mse_software@charter.net) Received: from mxip02a.cluster1.charter.net (mxip02a.cluster1.charter.net [209.225.28.132]) by mxsf20.cluster1.charter.net (8.12.11/8.12.11) with ESMTP id jAK7opKm004938 for ; Sun, 20 Nov 2005 02:50:51 -0500 Received: from 68-116-0-143.dhcp.knwk.wa.charter.com (HELO yak.mseubanks.net) ([68.116.0.143]) by mxip02a.cluster1.charter.net with ESMTP; 20 Nov 2005 02:50:51 -0500 X-IronPort-AV: i="3.97,352,1125892800"; d="scan'208"; a="1629044650:sNHT16011640" From: Mike Eubanks To: freebsd-questions@freebsd.org In-Reply-To: <1132465267.1524.30.camel@yak.mseubanks.net> References: <1132465267.1524.30.camel@yak.mseubanks.net> Content-Type: text/plain Date: Sat, 19 Nov 2005 23:50:48 -0800 Message-Id: <1132473048.12843.26.camel@yak.mseubanks.net> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: NFS consumes network bandwidth X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mse_software@charter.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2005 07:50:53 -0000 On Sat, 2005-11-19 at 21:41 -0800, Mike Eubanks wrote: > I'm really not sure where to start on this one. No changes have been > made on the server for some time. Both are running 5.4-STABLE. > > On the client (my workstation) I cleaned out my home directory to > freshen up my Gnome desktop. Shortly thereafter, the network load began > to exhibit a consistent patern of stepping from 0% usage to roughly 80% > usage, something it hasn't done in the past. Every time I use an > application such as Mozilla, Evolution, etc. (in Gnome 2.10) the network > usage drops immediately to 0% for a short period, say 10-30 seconds, and > begins to accumulate gradually again. On the other hand, network load > does not fall off when running any process as a daemon, or from the > shell. > > I used `tcpdump' to dump the packets being sent on the interface. It > appears NFS is generating all of the traffic, although, I'm not sure why > because the actual mounts are not heavily used, or at least haven't > demonstrated this behaviour in the past. I unmounted all NFS file > systems and the network load dropped off completely and did not return. > > I did move the mount points directly to my home directory, rather than > linking to a mount point that existed in /mnt. This is about the only > other thing I can think of, altough, I'm hoping someone could tell me a > bit more before I reverse the changes. > I reversed the mountpoint changes, although, it still exhibits the same behaviour. Below is an illustration of the current setup. server:share1 --> maps to --> client:/mnt/myname/share1 server:share2 --------------> client:/mnt/myname/share2 server:share3 --------------> client:/mnt/myname/share2 The link from home directory on client machine looks like the following: /usr/home/myname/mnt/imports -> /mnt/myname After I access the NFS filesystem, the load increases to a constant 80% as described above. Below is a snippet of the `tcpdump -c 1000 -vv -i xl0' command for all traffic. I removed the timestamps and abbreviated the client and server host names. The only two hosts talking are the client and server, and all traffic is identical to the following. client.220312819 > server.nfs: 96 fsstat [|nfs] server.nfs > client.220312819: reply ok 168 fsstat POST: DIR 755 ids 1001/0 [|nfs] client.220312820 > server.nfs: 96 fsstat [|nfs] server.nfs > client.220312820: reply ok 168 fsstat POST: DIR 755 ids 1001/0 [|nfs] client.220312821 > server.nfs: 96 fsstat [|nfs] server.nfs > client.220312821: reply ok 168 fsstat POST: DIR 755 ids 0/0 [|nfs] client.220312822 > server.nfs: 96 fsstat [|nfs] server.nfs > client.220312822: reply ok 168 fsstat POST: DIR 755 ids 0/0 [|nfs] client.220312823 > server.nfs: 96 fsstat [|nfs] server.nfs > client.220312823: reply ok 168 fsstat POST: DIR 755 ids 0/0 [|nfs] -- Mike Eubanks