From: vikki@e40-008-9.MIT.EDU (Vikki King)
Subject: Re: Trouble using an NFS filesystem
Organization: J. Random Misconfigured Site
X-Newsreader: Tin 1.1 PL4
Date: Fri, 11 Sep 1992 18:03:45 GMT
X-Posted-From: e40-008-9.mit.edu
X-Posted-Through: sol.ctr.columbia.edu

Hey Hey!

	Thanks for the pointers Terry!  The problems were my syntax for the
mount command and my permissions on the Netware/NFS server.  After fixing both,
I can access everything.  I'm having some new difficulties now.
	When I initially got priviledges set correctly, I was able to copy
files as large as I wanted *to* an NFS filesystem.  However, I could only
*read* successfully very small files from the NFS filesystem.  Anything larger
that a few kilobytes >= ~25K and the read operation would hang.  I would
get a message saying that the NFS server was not responding.  I checked the
NFS server but it was fine.  I rebooted 386bsd and all was well again until I
tried to do any king of reads of big files.  Same problem all over again.
Several times while trying all this I even got some panics.
	Well, I then remembered someone writing something about using the
added options of -o rsize-4096, wsize=4096 when mounting.  Yayy!!  That
helped out a lot.  I am now able to read most things, *except* REALLY
big files, like the one I've tried so far is >50MB.  I get the same troubles
with NFS errors and panics all over again.  Thinking that if a little is
good more is better, I increased the rsize/wsize settings to 6144 first and
then 8192 next.  That didn't help.  When set to 6144, Doing an extract against
the etc01.?? files produced the error from extract that all of the files were
corrupt.  At that point, I switched back to 4096, cat'd all the etc01.?? stuff
to a .Z file, uncompressed it to 51MB, tried to cpio it by hand.  Again, the
same crashing problems.  I finally ftp'd the 51MB file to my local disk and
cpio'd it back onto a symbolic link to the NFS volume.
	Do you think there are some problems with the NFS client part of
386bsd or do I just still have more to learn about NFS tuning? :-)

Overall, I have to say that I think this whole 386bsd thing is MOST coool!!!

-John
jackson@a1.mec;.mass.edu

terry@thisbe.Eng.Sandy.Novell.COM (Terry Lambert) writes:
: In article <1992Sep10.162146.1@woods.ulowell.edu> jackson@woods.ulowell.edu writes:
: >Now, for something related:
: > 
: >After ifconfig'ing ec0 and successfully ftp'ing/ping'ing a host on our net,
: >I am having problems trying to access an NFS server.  The NFS server is a
: >netware 3.11 box with Netware NFS v1.1.  I can get the server volume to mount
: >on the 386bsd filesystem and running df gives an accurate report of the space
: >available, but I am unable to do anything in the directory where the NFS
: >volume is mounted.  Trying to do an ls or cp'ing something into that directory
: >just gives me a permission denied error.  Doing an ls -l of the mount
: >directory after I've mounted the volume shows the privledges as being:
: > 
: > drwx------     4 root          512 Sep 9 16:30 mcet1/    
: > 
: >It would seem as if I had the proper privledges, right?  Last, if I explicitly
: >try to mount the NFS volume by hand with the command line:        
: > 
: > # mount /bsd386/@mcet1: /mcet1 (I know, I know, it should be /386bsd/ :-) )
: > 
: >I get a message that reads "Can't get net id for host".  I can't figure out if
: >I've got something set up incorrectly on the Netware NFS hosts's side or if
: >the problem is somewhere in how I've configured the 386bsd system.  Anyone
: >want to offer any suggestions?    
: 
: 1.	What are the permissions on the directory you are mounting over?  I
: 	suspect that you don't have permission.
: 
: 2.	This information implies that you are root trying to access
: 	something in a directory owned by root on a remote machine.  Have
: 	you done a "root=<client host name>" as an option on the exporting
: 	host?  If not, you are coming in as id -2 ("nobody") and will not
: 	be allowed to access the directory.  I realize that doing this is
: 	"a bit different" using NetWare as a server.
: 
: 3.	If you can't get an id for it, the host "mcet1" isn't in your hosts
: 	database.  If it is, perhaps the "<directory>@<host>" syntax is
: 	broken on your NFS.  Try "<host>:<directory>" instead.  One way
: 	this "break" might show up is your use of a ":" and an "@" in the
: 	same line, configuing BFS into thinking "/bsd386/@mcet1" was the
: 	host name and "" was the file name (the part with no whitespace
: 	seperator following the colon is empty in the line you gave).
: 
: Please post a followup telling which, if any of these, solved your problem.
: 
: 
: 					Terry Lambert
: 					terry_lambert@gateway.novell.com
: 					terry@icarus.weber.edu
: 
: ---
: Disclaimer:  Any opinions in this posting are my own and not those of
: my present or previous employers.
Newsgroups: comp.unix.bsd