On Fri, Jan 14, 2011 at 5:02 PM, Mi Jinlong <mijinlong@xxxxxxxxxxxxxx> wrote: > > > hce : >> Thanks for your response. I've just found that nlockmgr did not >> respond when I run following command on the server. Is it a problem or >> it is normal? Anyway, the NFS is still working fine. > > No, it's not a problem. > It just a lack of NFSv3's file lock, if you try to lock NFSv3 file, > you must start the nfslock service both the client and server > (maybe other platform don't named nfslock). > > Because your normal NFS operation don't need file lock, > so NFSv3 is still working fine. Thanks. Good to know, so I don't need to worry about it. >> >> $ rpcinfo -t linux_server nlockmgr >> rpcinfo: RPC: Timed out >> program 100021 version 0 is not available >> >> $ rpcinfo -u linux_server nlockmgr >> rpcinfo: RPC: Timed out >> program 100021 version 0 is not available >> >> $ rpcinfo -p > > The linux_server and localhost are different machine ? > > linux_server is CentOS?? or MAC? > localhost is? The linux_server is a host for NFS server running CentOS. All commands were called in the NFS server. Anyway, the MAC clients sometime crashed or sometime worked very slow when the NFS server got rpc.statd[2448]: Can't callback .... If I understand it correct, it should not cause the MAC networking problem, then we have to look at the problem in other places. Thank you. Kind regards. > > -- > thanks, > Mi Jinlong > >> program vers proto port >> 100000 2 tcp 111 portmapper >> 100000 2 udp 111 portmapper >> 100024 1 udp 895 status >> 100024 1 tcp 898 status >> 100011 1 udp 806 rquotad >> 100011 2 udp 806 rquotad >> 100011 1 tcp 809 rquotad >> 100011 2 tcp 809 rquotad >> 100003 2 udp 2049 nfs >> 100003 3 udp 2049 nfs >> 100003 4 udp 2049 nfs >> 100021 1 udp 32794 nlockmgr >> 100021 3 udp 32794 nlockmgr >> 100021 4 udp 32794 nlockmgr >> 100003 2 tcp 2049 nfs >> 100003 3 tcp 2049 nfs >> 100003 4 tcp 2049 nfs >> 100021 1 tcp 57164 nlockmgr >> 100021 3 tcp 57164 nlockmgr >> 100021 4 tcp 57164 nlockmgr >> 100005 1 udp 828 mountd >> 100005 1 tcp 831 mountd >> 100005 2 udp 828 mountd >> 100005 2 tcp 831 mountd >> 100005 3 udp 828 mountd >> 100005 3 tcp 831 mountd >> >> On Fri, Jan 14, 2011 at 1:37 PM, Mi Jinlong <mijinlong@xxxxxxxxxxxxxx> wrote: >>> >>> hce : >>>> Hi, >>>> >>>> I am running nfs server on a CentOS 5, it works fine for all >>>> connections from linux, windows clients. Mac clients worked fine for >>>> coping some regular files, but it could not copy mac packaging file >>>> with the extension *.dmg, it stuck with an error "nfs server lockd not >>>> responding", at the same time the server got a log message of >>>> "rpc.statd[2448]: Can't callback linux_server (100021,4), giving up". >>>> >>>> Appreciate advice what could cause that problem and how could fix it? >>> Hi hce, >>> >>> You use NFSv3, >>> the NFSv3's file lock service depend on NLM(Network Lock Manager), >>> that need a user space program named rpc.statd to support service >>> like this: >>> >>> | nfs client | nfs server >>> ------------------------------------------------- >>> | | >>> user space | rpc.statd <---> rpc.statd >>> | ^ | ^ >>> --------------------|------------------------|---- >>> | v | v >>> kernel | lockd <---> lockd >>> >>> when your nfs client is a MAC, maybe Mac's user space don't support >>> a program as rpc.statd, or you don't make the program run correctly. >>> >>> Maybe you can use NFSv4 to avoid this problem. >>> >>> >>> -- >>> ---- >>> thanks >>> Mi Jinlong >>> >>> >> >> > > -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
