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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
