mount 错误 “RPC: failed to contact local rpcbind server (errno 5).”解决方法

通过机顶盒mount build server的nfs时

 

root:# mount -t nfs 192.168.100.21:/home/cnh01994/nfsroot /mnt/nfs
rpcbind: server localhost not responding, timed out
RPC: failed to contact local rpcbind server (errno 5).
rpcbind: server localhost not responding, timed out
RPC: failed to contact local rpcbind server (errno 5).
lockd_up: makesock failed, error=-5
rpcbind: server localhost not responding, timed out
RPC: failed to contact local rpcbind server (errno 5).

 

加入-o nolock选项，root:# mount -o nolock -t nfs 192.168.100.21:/home/cnh01994/nfsroot /mnt/nfs则工作正常。

查询网上关于nolock的解释如下：

The nolock option prevents the exchange of file lock information between the NFS server and this NFS client. The server is not aware of file locks on this client, and vice versa.
Using the nolock option is required if the NFS server has its NFS file lock functionality in a broken or unimplemented state, but it works between any versions of NFS.
If another host accesses the same files as your application on this host, there may be problems if file lock information exchange is disabled.
A failure to maintain proper locking between a write operation on one host and a read operation on another may cause the reader to get incomplete or inconsistent data (reading a line/record/data structure that is only partly written).
A locking failure between two writers is likely to cause data loss/corruption, as the later write overwrites the earlier one. The changes made by the earlier write operation can be lost.
The error message "No locks available" would seem that the file locks are a finite resource, and all the available locks are in use. You might wish to check if the number of file locks per user is limited by "ulimit -x" settings, both on the NFS client and on the server.
You might also take a look at the logs of the NFS server, to see if there are any locking-related messages. Because the NFS server needs to keep track of the sum total of the locks of all its clients, any problem with lock resources would probably be seen there first.

可能是因为多个终端同时mount nfs引起，因为盒子本身就是通过nfs，boot起来的

本文转自“ 叶落花开” 博客， http://wb127.blog.51cto.com/2232662/401732