Odd Linux NFS server behavior.
Posted on 1997-05-08
Hello. I seem to be having trouble when mounting the root directory of a Slackware96 (08/96) machine to any other machine on our network (Linux PCs, SGIs, and HPs). The problem is twofold: files in directories not world accessible are silently ignored, and no file is writable.
OK, for those of you experts still reading 8^), here are some specifics.
The NFS server (the Slackware96 machine) has the following /etc/exports file:
server:~/# cat /etc/exports
# See exports(5) for a description.
# This file contains a list of all directories exported to other computers.
# It is used by rpc.nfsd and rpc.mountd.
The machine has been completely rebooted with this file in place, so the daemons should be fresh.
On the client (for example, a Slackware 3 machine), I run the following mount command (where /server exists and is drwxr-xr-x):
client:~/# mount server:/ /server
The command succeeds with no output. And, if I then try something like the following:
client:~/# su - alizhan
client:~/% ls -l
drwx------ 5 alizhan pmc 1024 Apr 22 14:21 Personal/
drwxr-xr-x 6 alizhan pmc 1024 Apr 14 16:14 Public/
drwx------ 3 alizhan pmc 1024 May 6 14:07 Rubbish/
drwx------ 6 alizhan pmc 1024 Apr 14 16:15 Temp/
everything seems to work just fine. Then the problems start showing up. For example:
client:~/% ls -Al Public
-rw-r--r-- 1 alizhan pmc 4324780 Apr 14 16:12 42400.stl
drwxr-xr-x 3 alizhan pmc 1024 Apr 14 16:14 Dev
drwxr-xr-x 2 alizhan pmc 1024 Apr 14 16:12 Dos
drwxr-xr-x 2 alizhan pmc 1024 Apr 14 16:12 InBox
drwxr-xr-x 9 alizhan pmc 1024 Apr 14 16:13 Unix
-rw-r--r-- 1 alizhan pmc 8735161 Apr 14 16:12 emacs-19_34.zip
client:~/% ls -Al Personal
client:~/% ls > foo
bash: foo: No such file or directory
The first command works, the second and third don't. The Personal/ directory is _not_ empty, and I can think of no reason the file foo cannot be created (or clobbered, for that matter) as ~alizhan/ is drwxr-xr-x.
I have made sure that the UID/GID are the same between the two machines, and both machines know the address of the other. I have tried explicitly manipulating the rw, rsize, and wsize parameters of the mount command, as well. No effect.