Cannot write to NFS-mounted directories

I've got two Red Hat Linux boxes, running Red Hat 6.0.  I can successfully mount an NFS directory on the client, and list the files, and display them.  They all appear to have read-write priviledges, but I'm unable to edit a file, or write in any way to the NFS-mounted directory. This problem arises both as root and as an ordinary user. The NFS server has an /etc/exports file without tabs, and with a (rw) code immediately after the client name (no spaces).  The machines as also linked in a NIS server-client relationship, running ypserv (the ypserv originally supplied on the RedHat CD didn't work properly with yppasswd).

A couple of oddities:
1. /proc/filesystems on the NFS server shows
nodev   proc
nodev   devpts

I had expected to see nfs in there, yet nfs support is now supposed to be modular, so hoping that I don't have to rebuild the kernel (worry!)

2. The showmount command described in RedHat's NFS-Tips web document is missing from my machines.

I'm obviously overlooking something simple here.  Many thanks in advance for any help.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

If you have an /etc/exports file, what did exportfs tell you?

> showmount .. is missing ..
Did you search with
      find / -name showmount
for it?
doystonAuthor Commented:
exportfs works fine, giving:

I've tried finding showmound with the find command, but no success.
Couple of things...

First off the showmount command is part of the knfsd-clients package you might want to install it there.

Second, more like an FYI the nfs filesystem support is only needed on the client therefor your server doesn't need it since it's not mount'n a nfs filesystem, you get the jist...

Third, make sure that your user is being looked up from NIS and not the local /etc/passwd file, but more importantly that your userid on the server match the userid on your client.

You need to add the no_root_squash option to the exports file to allow root to write to the filesystem (else it automagically gets mapped to the user nobody)

Hope this helps

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

can you get the reverse address resolution on your server for ?

> Third, make sure that your user is being looked up from NIS and not the local /etc/passwd file, ..
has no impact on mount requests, if you files or NIS or whatever
doystonAuthor Commented:
The user is definitely being looked up from the NIS password list (in fact the user does not even have an entry on the NFS/NIS client password machine file).

Could you clarify what you mean by 'reverse address resolution' on the server, as I don't fully understand you (Linux newbie here!).

assuming that is the client which requests the mount, could you do on the server:


if it reports an error, must be listed in /etc/hosts *AND* /the resolver (etc/hosts.conf) must be configure to use DNS and /etc/hosts
doystonAuthor Commented:
OK thanks- nslookup reports no errors, and correctly shows the DNS server as well as  Any other suggestions of things to try...?
do you have a DENY clause in /etc/hosts.deny (please read man hosts.access)
doystonAuthor Commented:
Problem solved: the fault was actually in the NIS part of the setup, not the NFS side of things.  I'd forgotten to increase my group id number to above the minimum defined in the yp makefile.  Once changed, everything works fine.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.