NFS troubles

My 1 year old daughter "rebooted" a machine at home "for" me. Now NFS
won't work between two machines.

I have 3 machines; let's call them server, client, and laptop. Each of
these machines can mount their own drives over NFS, not useful for too
much to me other than NFS debugging. All machines can mount the others
drives just fine *EXCEPT* that the laptop can no longer mount drives on
the server. The laptop/server NFS connection worked just fine before
the server reboot. When I try to mount a server drive on the laptop it
just hangs. Looking in /var/log/syslog on the laptop I see this:

Mar 20 18:48:15 laptop automount[25212]: >> mount clntudp_create: RPC:
Port mapper failure - RPC: Unable to receive
Mar 20 18:48:15 laptop automount[25212]: lookup(program): lookup for
server failed
Mar 20 18:48:15 laptop automount[25212]: failed to mount /net/server

I don't see anything in the server logs caused by the mount attempt.
dmesg on the server says this though:

nfsd: bad address count in freeclient!

That seems to be from the time it booted.

My /etc/exports file on the server says this:

/home 192.168.1.2(rw,no_root_squash,sync)
/home 192.168.1.3(rw,no_root_squash,sync)
/home 192.168.1.4(rw,no_root_squash,sync)

My /etc/hosts.allow file on the server says this:

ALL: 192.168.1.2
ALL: 192.168.1.3
ALL: 192.168.1.4

I don't think those files would be the source of the trouble since I
didn't change them; the machine just rebooted. I don't see any
difference in how the server is configured to respond to the client
versus how it's configured to respond to the laptop.

The server is Mandrake 9.0 running a 2.4 kernel. The client and
laptop are both Mandrake 10.1 running a 2.6.8 kernel.

Anyone know how I can further debug my problem and get the laptop to
mount the server via NFS again?

Thanks...


--
PLEASE post a SUMMARY of the answer(s) to your question(s)!
Show Windows & Gates to the exit door.
Unless otherwise noted, the statements herein reflect my personal
opinions and not those of any organization with which I may be affiliated.

Kevin <(E-Mail Removed)> wrote:
> I have 3 machines; let's call them server, client, and laptop. Each of
> these machines can mount their own drives over NFS, not useful for too
> much to me other than NFS debugging. All machines can mount the others
> drives just fine *EXCEPT* that the laptop can no longer mount drives on
> the server. The laptop/server NFS connection worked just fine before
> the server reboot.

I have a little more info. The server's /var/log/syslog says this when
I get a successful mount from the client:

Mar 20 19:56:06 server rpc.mountd: export request from 192.168.1.2
Mar 20 19:56:06 server rpc.mountd: authenticated mount request from
client.nowhere.com:984 for /home (/home)
Mar 20 19:57:09 server rpc.mountd: authenticated unmount request from
client.nowhere.com:615 for /home (/home)

The server's /var/log/syslog says this when I get an unsuccessful mount
from the laptop:

Mar 20 19:03:50 server rpc.mountd: export request from 192.168.1.4

I'm certain there's a big clue in the fact that the laptop never gets
authenticated. I don't know why that would be.

Any thoughts people?

Thanks...

--
PLEASE post a SUMMARY of the answer(s) to your question(s)!
Show Windows & Gates to the exit door.
Unless otherwise noted, the statements herein reflect my personal
opinions and not those of any organization with which I may be affiliated.

In comp.os.linux.misc Kevin <(E-Mail Removed)>:
> My 1 year old daughter "rebooted" a machine at home "for" me. Now NFS
> won't work between two machines.
[..]

> just hangs. Looking in /var/log/syslog on the laptop I see this:

> Mar 20 18:48:15 laptop automount[25212]: >> mount clntudp_create: RPC:
> Port mapper failure - RPC: Unable to receive

Do as the message suggests, start portmapper on the laptop and
make sure it runs in addition to rpc.lockd/rpc.statd, check on
the laptop with 'rpcinfo -p localhost'. Or/and try the NFS HOWTO
(www.tldp.org) if problems persist.

[..]

Good luck

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 319: Your computer hasn't been returning all the
bits it gets from the Internet.

Hi,


I also had trouble with my NFS exports. This probably is no solution as
You say it worked before, but try putting Your exports on one line like

/home 192.168.1.2(rw,no_root_squash,sync) 192.168.1.3(rw,no_root_squash,sync) 192.168.1.4(rw,no_root_squash,sync)

and reexport using exportfs -ra.

Maybe You upgraded Your NFS distribution or kernel version and it doesn't
work with several lines for the same export.


Paul

I had to re-install the quota package on my laptop. I recall deciding
that I didn't need quotas on my system and blindly removed the package,
which deleted /usr/sbin/rpc.rquotad, which was apparently required for
the laptop to mount remote drives via NFS. I reinstalled quota and all
is well now. Comparing the output of 'rpcinfo -p' on a working client
versus the busted laptop pointed me in the direction of the solution.

Thanks....

--
PLEASE post a SUMMARY of the answer(s) to your question(s)!
Show Windows & Gates to the exit door.
Unless otherwise noted, the statements herein reflect my personal
opinions and not those of any organization with which I may be affiliated.

Earlier I <(E-Mail Removed)> wrote:
> I have 3 machines; let's call them server, client, and laptop.
> Each of these machines can mount their own drives over NFS,
> not useful for too much to me other than NFS debugging. All
> machines can mount the others drives just fine *EXCEPT* that
> the laptop can no longer mount drives on the server. The
> laptop/server NFS connection worked just fine before the server
> reboot. When I try to mount a server drive on the laptop it
> just hangs.

Then I thought I had it fixed, and wrote:

> I had to re-install the quota package on my laptop. I recall
> deciding that I didn't need quotas on my system and blindly
> removed the package, which deleted /usr/sbin/rpc.rquotad, which
> was apparently required for the laptop to mount remote drives
> via NFS. I reinstalled quota and all is well now. Comparing
> the output of 'rpcinfo -p' on a working client versus the
> busted laptop pointed me in the direction of the solution.

Last night I discovered that while the connection works, it
runs very slowly. From the client or the server I can initiate
NFS transfers with the laptop which will move data in either
direction through eth1 on the laptop maybe 10-20X faster than
data movement when initiated on the laptop. Any guesses as to
what I could do about this?

Thanks....


--
PLEASE post a SUMMARY of the answer(s) to your question(s)!
Show Windows & Gates to the exit door.
Unless otherwise noted, the statements herein reflect my personal
opinions and not those of any organization with which I may be affiliated.