NFS mount problem

ramesh14 · 12-03-2009, 04:49 AM

Hi all,

In my office i've installed fedora 12, when ever i was trying to access NFS share in LAN environment i was getting these errors.

$sudo mount x.x.x.x:/misc/export /misc/local , after executing this command i was getting these errors.

/usr/sbin/start-statd: line 8: /sbin/rpc.statd: Permission denied
/usr/sbin/start-statd: line 8: /sbin/rpc.statd: Success
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified

could any one please give me suggessions how to access NFS share.

Thanks alot.

donanap · 12-03-2009, 06:25 AM

Hi Ramesh,

Please run this command and post your results:

Code:

rpcinfo -p

You should see an output like this:

Quote:

100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100011 1 udp 749 rquotad
100011 2 udp 749 rquotad
100005 1 udp 759 mountd
100005 1 tcp 761 mountd
100005 2 udp 764 mountd
100005 2 tcp 766 mountd
100005 3 udp 769 mountd
100005 3 tcp 771 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
300019 1 tcp 830 amd
300019 1 udp 831 amd
100024 1 udp 944 status
100024 1 tcp 946 status
100021 1 udp 1042 nlockmgr
100021 3 udp 1042 nlockmgr
100021 4 udp 1042 nlockmgr
100021 1 tcp 1629 nlockmgr
100021 3 tcp 1629 nlockmgr
100021 4 tcp 1629 nlockmgr

If you are missing some of the listed items it means the daemons arent running/configued.
Good Luck.

vishesh · 12-03-2009, 06:31 AM

Whats your , entry in /etc/exports of nfs server ?

Thanks

ramesh14 · 12-03-2009, 10:35 PM

hi Donanap

i run the command rpcinfo -p
i was getting this out put
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 57922 status
100024 1 tcp 42874 status
100021 1 udp 43382 nlockmgr
100021 3 udp 43382 nlockmgr
100021 4 udp 43382 nlockmgr
100021 1 tcp 42703 nlockmgr
100021 3 tcp 42703 nlockmgr
100021 4 tcp 42703 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100005 1 udp 41670 mountd
100005 1 tcp 38684 mountd
100005 2 udp 41670 mountd
100005 2 tcp 38684 mountd
100005 3 udp 41670 mountd
100005 3 tcp 38684 mountd
but i was unable to mount local nfs share plese guide me.....

chrism01 · 12-03-2009, 10:38 PM

As per your 1st post

Quote:

mount.nfs: rpc.statd is not running but is required for remote locking.

rpc.statd is not up....
See chap 18 http://www.linuxtopia.org/online_boo...ion/index.html

bret381 · 12-03-2009, 10:58 PM

also you can add the -o nolock option to your mount command

mount x.x.x.x:/share /mount_point nfs -o nolock

donanap · 12-04-2009, 01:13 AM

Hi Ramesh,

No one has told you how to start this rpc.statd daemon, so here a quick guide.

Firstly, in order for nfs to be working correctly make sure the portmapper is running:

Code:

/sbin/service portmap status

If it is running you your nfs service should work fine. If it is not running just run the following command to start portmapper:

Code:

/sbin/service portmap start

ensure to restart the nfs service after you have started the portmapper.

Code:

/sbin/service nfs restart

Now you must also start the nfslock module. nfslock service controls the rpc.statd daemon run the following command to start it.

Code:

/sbin/service nfslock start

run this command to see if nfslock is turned on automatically to start at boot up.

Code:

chkconfig --list nfslock

To set nfslock to automatically start on boot, type the following command. ( Read the man pages for chkconfig, you can also specifyb which run levels to automatically start a service on)

Code:

chkconfig nfslock on

Good Luck, hope this fixes your problem.
Donanap.