From owner-freebsd-current Thu Oct 28 1:26: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0580A15067 for ; Thu, 28 Oct 1999 01:25:29 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id BAA19644 for ; Thu, 28 Oct 1999 01:25:16 -0700 Date: Thu, 28 Oct 1999 01:25:14 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: really draggy NFS access in -current? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the following setup for an alpha PC164 running a current -current (as in a kernel from the last day): farrago.feral.com > mount /dev/da0a on / (ufs, local, writes: sync 608 async 3306) procfs on /proc (procfs, local) mfs:30 on /tmp (mfs, asynchronous, local, writes: sync 2 async 7) bird:/export/home on /home (nfs) bird:/home/ncvs on /home/ncvs (nfs) bird:/space5/freebsd/FreeBSD-current/sys on /space/sys (nfs) bird:/space5/freebsd/FreeBSD-CVS on /cvs-src/FreeBSD-CVS (nfs) bird:/space5/freebsd/distfiles on /usr/ports/distfiles (nfs) /dev/da6a on /usr/obj (ufs, local, soft-updates, writes: sync 2 async 1) /dev/da5a on /usr/src (ufs, local, soft-updates, writes: sync 2 async 19415) Okay- I went home and left a cvs update going on /usr/src - reading from a local CVSUP repository NFS mounted on /home/ncvs. The server is a Sun SS1000 Solaris 2.6 box. 6 hours later, the cvs update is still chugging slowly along- top shows cvs as: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 275 mjacob 2 0 8704K 7616K sbwait 1:28 1.90% 1.90% cvs most of the time. Just to check that something wasn't broken for da5, I did a test dd writing to a file just now and it happily munched along at 4MB/s. The filesystem *is* a fat block fs: a: 4304896 0 4.2BSD 8192 32768 16 # (Cyl. 0 - 267*) I suppose the blockage could be at the ufs end... Anyone have a pointer as to what try to narrow this down- mainly to save me the trouble of actually thinking about it (got a lot else on mind)? Unacceptably bad something or others here..... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message