Hi, I'm having a locking problem in a linux client, kernel 2.4.18 with a NetApps filer, F760, NetApp Release 6.1.2R3: Sat Apr 6 02:23:00 PST 2002.
In fstab I have:
filer.nfs:/vol/home /netapp nfs rw,bg,lock,intr,rsize=8192,wsize=8192,retry=5,retrans=130,timeo=14
in the server, dmesg:
lockd: cannot monitor 192.168.1.104 lockd: cannot monitor 192.168.1.104 lockd: cannot monitor 192.168.1.104
in the server, rpcinfo:
homes1:/etc/init.d# rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 32768 nlockmgr 100021 3 udp 32768 nlockmgr 100024 1 udp 809 status 100024 1 tcp 811 status
What can be causing the lockd: cannot monitor?
TIA.
Do you have a firewall on the linux box ?
/etc/hosts.allow, deny etc
Also, you definitely want to upgrade to 2.4.20(with ac2 patch) if you want linux and netapp to behave well.
There is a pretty well-written article by Chuck Lever on NetApp's website. http://www.netapp.com/tech_library/3183.html
Good Luck.
On Fri, 5 Sep 2003, Jose Celestino wrote:
Date: Fri, 5 Sep 2003 18:08:57 +0100 From: Jose Celestino japc@co.sapo.pt To: toasters@mathworks.com Subject: Problems with locking
Hi, I'm having a locking problem in a linux client, kernel 2.4.18 with a NetApps filer, F760, NetApp Release 6.1.2R3: Sat Apr 6 02:23:00 PST 2002.
In fstab I have:
filer.nfs:/vol/home /netapp nfs rw,bg,lock,intr,rsize=8192,wsize=8192,retry=5,retrans=130,timeo=14
in the server, dmesg:
lockd: cannot monitor 192.168.1.104 lockd: cannot monitor 192.168.1.104 lockd: cannot monitor 192.168.1.104
in the server, rpcinfo:
homes1:/etc/init.d# rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 32768 nlockmgr 100021 3 udp 32768 nlockmgr 100024 1 udp 809 status 100024 1 tcp 811 status
What can be causing the lockd: cannot monitor?
TIA.
-- Jose Celestino | http://xpto.org/~japc/files/japc-pgpkey.asc
"Lately, the only thing keeping me from becoming a serial killer is my distaste for manual labor." -- Dilbert
/dev/null
devnull@adc.idt.com
Words by devnull@adc.idt.com [Fri, Sep 05, 2003 at 01:49:45PM -0400]:
Do you have a firewall on the linux box ?
/etc/hosts.allow, deny etc
Also, you definitely want to upgrade to 2.4.20(with ac2 patch) if you want linux and netapp to behave well.
There is a pretty well-written article by Chuck Lever on NetApp's website. http://www.netapp.com/tech_library/3183.html
Good Luck.
Just for the record. For anyone with the same problem; I upgraded the nfs-utils to the latest version on the Debian Woody box and the problem disappeared.
The solution appeared on some newsgroups after some search (which I should have done before, I know :/ But as a reminder I will leave this. Will not even cut the remaining of the e-mail so that it best fits the search engines :) ).
On Fri, 5 Sep 2003, Jose Celestino wrote:
Date: Fri, 5 Sep 2003 18:08:57 +0100 From: Jose Celestino japc@co.sapo.pt To: toasters@mathworks.com Subject: Problems with locking
Hi, I'm having a locking problem in a linux client, kernel 2.4.18 with a NetApps filer, F760, NetApp Release 6.1.2R3: Sat Apr 6 02:23:00 PST 2002.
In fstab I have:
filer.nfs:/vol/home /netapp nfs rw,bg,lock,intr,rsize=8192,wsize=8192,retry=5,retrans=130,timeo=14
in the server, dmesg:
lockd: cannot monitor 192.168.1.104 lockd: cannot monitor 192.168.1.104 lockd: cannot monitor 192.168.1.104
in the server, rpcinfo:
homes1:/etc/init.d# rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 32768 nlockmgr 100021 3 udp 32768 nlockmgr 100024 1 udp 809 status 100024 1 tcp 811 status
What can be causing the lockd: cannot monitor?
TIA.
--
-
devnull＠adc.idt.com -
Jose Celestino