Questions about NFS3 NLM,NSM lock error
Questions about NFS3 NLM,NSM lock error: Client(rpcbind ,rpc-statd/nfslock server is ok, rpc.statd running ): in nfs-ganesha mount point: touch f1; exec 200>f1; flock -xn 200 [error: on lock available ] Server nfs-ganesha log: nsm_monitor :Can not monitor ::ffff:10.10.10.102 SM_MON ret 5 : RPC: Timed out client rpcdebug log : Jul 13 15:28:51 cu09 kernel: lockd: get host 10.10.10.212 Jul 13 15:28:51 cu09 kernel: lockd: get host 10.10.10.212 Jul 13 15:28:51 cu09 kernel: lockd: nsm_monitor(10.10.10.212) Jul 13 15:28:51 cu09 kernel: lockd: call procedure 2 on 10.10.10.212 Jul 13 15:28:51 cu09 kernel: lockd: nlm_bind_host 10.10.10.212 (10.10.10.212) Jul 13 15:28:51 cu09 kernel: lockd: next rebind in 60000 jiffies Jul 13 15:29:16 cu09 kernel: lockd: server returns status 2 Jul 13 15:29:16 cu09 kernel: lockd: release client host 10.10.10.212 Jul 13 15:29:16 cu09 kernel: lockd: release client host 10.10.10.212 Jul 13 15:29:16 cu09 kernel: lockd: clnt proc returns -37 What is the cause of the above? 【Client】 [root@fat01 ~]# uname -a Linux fat01 3.10.0-862.el7.x86_64 #1 SMP Fri Apr 20 16:44:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [root@fat01 ~]# [root@fat01 ~]# lsb_release -a LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch Distributor ID: CentOS Description: CentOS Linux release 7.5.1804 (Core) Release: 7.5.1804 Codename: Core root@fat01 ~]# rpm -qa|grep nfs texlive-psnfss-svn23394.9.2a-38.el7.noarch libnfsidmap-0.25-19.el7.x86_64 nfs-utils-1.3.0-0.54.el7.x86_64 texlive-mfnfss-svn19410.0-38.el7.noarch nfs4-acl-tools-0.3.3-17.el7.x86_64 [root@fat01 ~]# rpm -qa|grep rpc xmlrpc-c-client-1.32.5-1905.svn2451.el7.x86_64 xmlrpc-c-1.32.5-1905.svn2451.el7.x86_64 rpcbind-0.2.0-44.el7.x86_64 libtirpc-0.2.4-0.10.el7.x86_64 kdepimlibs-kxmlrpcclient-4.10.5-4.el7.x86_64 【server】 ganesha:NFS-Ganesha Release = V2.7.3 -- Best Regards! ********************************************* Linjie Zang ( Master ) Dept. of Electronics Engineering Faculty of Information Engineering Zhengzhou University Science Road 100, Zhengzhou, Henan 450001 P.R.China Email:linjiez@163.com Phone: +86 152-251-22667
nsm_monitor :Can not monitor ::ffff:10.10.10.102 SM_MON ret 5 : RPC: Timed out
As you know Ganesha needs to talk to rpc.statd on localhost for granting an NLM lock. The client IP address is 10.10.10.102 but statd is unable to monitor. Ganesha waits for only 3 seconds for this, but the statd might be spending too much time doing reverse DNS lookup. Maybe, have an entry in the /etc/hosts for that IP address and see if that works. Increasing the timeout maybe an option but I am not sure if statd needs a name for the client's IP address. Regards, Malahal. On Tue, Jul 14, 2020 at 4:41 PM 臧林劼 <15225122667@163.com> wrote:
Questions about NFS3 NLM,NSM lock error: Client(rpcbind ,rpc-statd/nfslock server is ok, rpc.statd running ): in nfs-ganesha mount point:
touch f1; exec 200>f1; flock -xn 200 [error: on lock available ]
*Server nfs-ganesha log:* nsm_monitor :Can not monitor ::ffff:10.10.10.102 SM_MON ret 5 : *RPC: Timed out*
client rpcdebug log : Jul 13 15:28:51 cu09 kernel: lockd: get host 10.10.10.212 Jul 13 15:28:51 cu09 kernel: lockd: get host 10.10.10.212 Jul 13 15:28:51 cu09 kernel: lockd: nsm_monitor(10.10.10.212) Jul 13 15:28:51 cu09 kernel: lockd: call procedure 2 on 10.10.10.212 Jul 13 15:28:51 cu09 kernel: lockd: nlm_bind_host 10.10.10.212 (10.10.10.212) Jul 13 15:28:51 cu09 kernel: lockd: next rebind in 60000 jiffies Jul 13 15:29:16 cu09 kernel: lockd: server returns status 2 Jul 13 15:29:16 cu09 kernel: lockd: release client host 10.10.10.212 Jul 13 15:29:16 cu09 kernel: lockd: release client host 10.10.10.212 Jul 13 15:29:16 cu09 kernel: lockd: clnt proc returns -37
*What is the cause of the above?*
【Client】 [root@fat01 ~]# uname -a Linux fat01 3.10.0-862.el7.x86_64 #1 <https://github.com/nfs-ganesha/nfs-ganesha/pull/1> SMP Fri Apr 20 16:44:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [root@fat01 ~]# [root@fat01 ~]# lsb_release -a LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch Distributor ID: CentOS Description: CentOS Linux release 7.5.1804 (Core) Release: 7.5.1804 Codename: Core
root@fat01 ~]# rpm -qa|grep nfs texlive-psnfss-svn23394.9.2a-38.el7.noarch libnfsidmap-0.25-19.el7.x86_64 nfs-utils-1.3.0-0.54.el7.x86_64 texlive-mfnfss-svn19410.0-38.el7.noarch nfs4-acl-tools-0.3.3-17.el7.x86_64 [root@fat01 ~]# rpm -qa|grep rpc xmlrpc-c-client-1.32.5-1905.svn2451.el7.x86_64 xmlrpc-c-1.32.5-1905.svn2451.el7.x86_64 rpcbind-0.2.0-44.el7.x86_64 libtirpc-0.2.4-0.10.el7.x86_64 kdepimlibs-kxmlrpcclient-4.10.5-4.el7.x86_64 【server】 ganesha:NFS-Ganesha Release = V2.7.3
--
*Best Regards! * ********************************************* Linjie Zang ( Master ) Dept. of Electronics Engineering Faculty of Information Engineering Zhengzhou University Science Road 100, Zhengzhou, Henan 450001 P.R.China Email:linjiez@163.com Phone: +86 152-251-22667
_______________________________________________ Support mailing list -- support@lists.nfs-ganesha.org To unsubscribe send an email to support-leave@lists.nfs-ganesha.org
Thank you for your help , How to configure the reverse DNS lookup timeout,I will try to modify the timeout option. 'statd needs a name for the client's IP address',Is this configured on the server side? I have verified that if ganesha nfs_param.core_param.nsm_use_caller_name =true, you must configure hostname and client ip in /etc/hosts(server side), otherwise it will fail, why? Thank you again for your help, I hope to know this module. Best Regards Jimmy Zang
participants (3)
-
813527264@qq.com -
Malahal Naineni -
臧林劼