> Hello list :) > > This is my first post here, so if it's in the wrong place, or if I've > not read the appropriate documentation, please feel free to send me a > link to the relevant bits. I've tried searching the archives, and the > internet at large, but haven't yet come across anything that's helped. ... snip ... > I'm seeing these messages in the file server's system log: > > Jul 30 09:37:17 fs0 kernel: [1810036.560046] statd: server localhost > not responding, timed out > Jul 30 09:37:17 fs0 kernel: [1810036.560053] nsm_mon_unmon: rpc > failed, status=-5 > Jul 30 09:37:17 fs0 kernel: [1810036.560064] lockd: cannot monitor node2 > Jul 30 09:38:22 fs0 kernel: [1810101.384027] statd: server localhost > not responding, timed out > Jul 30 09:38:22 fs0 kernel: [1810101.384033] nsm_mon_unmon: rpc > failed, status=-5 > Jul 30 09:38:22 fs0 kernel: [1810101.384044] lockd: cannot monitor node0 > It looks like that nfslock service(statd) not running, please try run the followed command, # service rpcbind start # service nfslock restart -- Regards Bian Naimeng -- 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
