*BSD News Article 16358


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!uniwa!nodecg.ncc.telecomwa.oz.au!tdwyer
From: tdwyer@nodecg.ncc.telecomwa.oz.au (Terry Dwyer 4915161)
Subject: NFS mount probs with NetBSD-0.8
Organization: Regional Network Systems Group, Perth
Date: Fri, 21 May 1993 10:03:52 GMT
Message-ID: <1993May21.100352.8272@nodecg.ncc.telecomwa.oz.au>
Lines: 34



I have two NetBSD-0.8 boxes running, both 486DX 33's, and recently decided
to try NFS between them.  After looking over the configs for the kernel
in /sys/i386/conf, I decided to use NFS and NFS_CLIENT.  The kernel
compile was OK and I set up the /etc/rc to use the defaults for nfsd and
nfsiod by editing /etc/netstart.

After installing the new kernel on both machines and rebooting, I couldn't
eem to mount from either machine via the wd8013 cards.

After the NFS mount has been attempting to mount the remote machine for a 
while, the process dies with an interrupt message of some sort, (cant remember
exactly what iut is), and no mount is made. the following is my mount command:

mount -ro soft,intr,rsize=1024,wsize=1024,retry=5,retrans=5,timeo=5 \
      -v -t nfs bpserv:/usr /w

I was a little puzzled by this, as I have had no problems with NFS mounts
between 386bsd boxes before.  I thought I would have a look at what was
happening while the mount was being attempted with top.  Running top just
about made me fall out of my seat, nfsd was hogging the processor with
between 95 and 99% usage.  This was even before I attempted to run a
NFS mount.

Would anybody like to have a shot at explaining this, I sure can't.

Terry

-- 
-- 
   _-_|\    Terry Dwyer 	      E-Mail: tdwyer@nodecg.ncc.telecomwa.oz.au
  /     \   System Administrator      Phone: +61 9 491 5161  Fax: +61 9 221 2631
  *_.^\_/   Australian and Overseas Telecommunications Commission (AOTC)