Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!gmi!zombie.ncsc.mil!news.mathworks.com!newshost.marcam.com!usc!howland.reston.ans.net!news.sprintlink.net!nntp.earthlink.net!usenet From: shansen@earthlink.net (Skip Hansen) Newsgroups: comp.os.386bsd.bugs Subject: FreeBSD 2.0 NFS weirdness ? Date: 12 Feb 1995 15:46:48 GMT Organization: Un Organized Lines: 17 Message-ID: <3hlah8$efl@moon.earthlink.net> NNTP-Posting-Host: shansen.earthlink.net Mime-Version: 1.0 X-Newsreader: WinVN 0.93.11 I've just upgraded from FreeBSD 1.5.1 to 2.0-release and I now have a strange NFS problem. The first time I "ls" a subdirectory mounted via NFS it just returns without printing anything, all subsequent accesses work fine. I've successfully installed Xfree86 via NFS so I know it is working otherwise. My server is "SOSS" running on my DOS machine. I've used this combination to access my non-supported CD ROM on the DOS machine since 386BSD days. Heavy NFS access with 1.5.1 would stall occasionally, but I never had any other problems. Is this a known problem ? Read and write sizes are set to 1024 (the maximum supported by SOSS) if that provides a clue. By the way just in case no one else has mentioned it the new NFS wants "-r1024" instead of "-rsize=1024" as suggested by the installation script. Unfortunately since an "-o" is prepended to any options specified it's impossible correctly set the NFS read size using the installation script. Skip