Tim,
Thanks!
No firewall at all....same segment all working before.
The strange thing the netapp2 show 3 lines when you do
netapp2 lock status -f
========19081845:00000040
========19081845:00000060
========19081845:006352a7
it's cluster node netapp1 has hundreds of locks
Could be a poorly formed firewall rule that allows one way communication. In other words, a lock may be requested on a port. The filer responds on the same port but the return traffic is dropped (not rejected, dropped as rejecteded implies a response).
Usually a netstat -a on the client shows the culprit port.
--tmac
Sent from my Verizon Wireless BlackBerry
-----Original Message-----
From: "Linux Admin" < sysadmin.linux@gmail.com>
Date: Wed, 19 Dec 2007 17:55:16
To:"NetApp Toasters List" <toasters@mathworks.com >
Subject: file locking problem?
I have a process that runs ok on the local file system, but hang on filer
strace show that the last thing is tryong to do is acquire a lock
17:27:24 access("/netapp/file", W_OK) = 0 < 0.000013>
17:27:24 fstat64(13, {st_mode=S_IFREG|0755, st_size=741376, ...}) = 0 <0.000007>
17:27:24 fcntl64(13, F_SETLK, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}
and it hangs
on filer run the lock status -h and sm_mon -l <hostname> ...nothing
yet....there is a hostname in /etc/sm/monitor file
What is wrong?