通过机顶盒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).
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.
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起来的
©著作权归作者所有:来自51CTO博客作者wb127的原创作品,如需转载,请注明出处,否则将追究法律责任
0
收藏
推荐专栏更多
猜你喜欢
BAT批处理文件
oepnssh 无密码连接
启动网卡报错(Failed to start LSB: Bring up/down networking )解决办法总结
如何解决SVN Commit failed (details follow): Access denied
CentOS7 Failed to start LSB: Bring up/down解决方法
丢失Android系统库或者Conversion to Dalvik format failed with error 1错误的解决
docker Failed to get D-Bus connection 报错
SSH 登录失败:Host key verification failed 的处理方法
error: command 'gcc' failed with exit status 1 的解决办法
Docker容器使用问题:Failed to get D-Bus connection: Operation not permitted
“RPC服务不可用”的解决过程
Failed to load the JNI shared library jvm.dll
API网关如何实现对服务下线实时感知
浅谈ACL(访问控制列表)
Confluence 未授权 RCE (CVE-2019-3396) 漏洞分析
亿级日搜索量的美团如何构建高效的搜索系统?
玩转KVM:怎么追查KVM故障
mysql5.7.25主从同步图解(主:CentOS7.5,从win10)
springboot2+exporter+prometheus+grafana搭建监控体系
使用Alpine Linux和Oracle jre6构建Tomcat6镜像及应用容器化
扫一扫,领取大礼包
转载于:https://blog.51cto.com/wb127/401732
Ctrl+Enter 发布
发布
取消