Thanks, this gets me a little closer. What you write below leads me to believe that I need to grovel around in statd source (or sniff the wire) to find our just what it is sending at this moment.

"Keith Brown" keith@netapp.com writes:

4. Restart statd. Statd will send a STATMON packet to the filer that causes the filer to blow away all of the locks for that client.

Here's another quick tip for folks:

Vic Abell, the author of the o-so-useful lsof program (which knows about locks in some cases), also has a program called lslk for listing existing locks. Both lsof and lslk can be found at ftp://vic.cc.purdue.edu:/pub/tools/unix/. I've communicated with Mr. Abell, and he does not know of any specific tool to do what we've been discussing.

Peace, dNb