View Single Post

   
  #5 (permalink)  
Old 04-08-2008, 05:06 PM
J.O. Aho
 
Posts: n/a
Default Re: Gentoo NFS client does not connect following emerge -uDA world

Mark Hobley wrote:
> I am using Gentoo, and I updated the system using emerge -uDA. I am no
> longer able to mount NFS fileshares on my NFS server (running Debian).
>
> mount neptune:/volumes/vol3a/ /volumes/vol3a/
> mount: wrong fs type, bad option, bad superblock on
> neptune:/volumes/vol3a/,
> missing codepage or helper program, or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so


This indicates the version of nfs you try to mount ain't supported on the
client machine.

I suggest you run

rpcinfo -p neptune

on the client machine, and you should get an output something like:

program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 32769 status
100024 1 tcp 49475 status
100005 1 udp 32770 mountd
100005 1 tcp 54715 mountd
100005 2 udp 32770 mountd
100005 2 tcp 54715 mountd
100005 3 udp 32770 mountd
100005 3 tcp 54715 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100021 1 udp 32771 nlockmgr
100021 3 udp 32771 nlockmgr
100021 4 udp 32771 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100021 1 tcp 45138 nlockmgr
100021 3 tcp 45138 nlockmgr
100021 4 tcp 45138 nlockmgr

If you don't, then you don't even have the right to connect to the remote
machine with the nfs share.

You can also run "nfsstat" on the remote machine, this way you can see which
NFS version it runs (debian suxx on sharing the configuration through proc).


--

//Aho
Reply With Quote