On Fri, Sep 03, 2010 at 03:59:04PM -0400, Payne, Rich wrote:
No, sorry, wasn't clear about the part I was responding to.
You had:
"My machine:
========002c613d:00760cb9 NLM[10.44.128.20,41648]: 0:0 1 GRANTED (0xffffff08d3686428)
Which would mean that process 41648 from host 10.44.128.20 has a lock on the file.
Yup. I understood you. But because I had another lock where instead of "41648", I had a "3", I couldn't belive that it was the PID.
So maybe it's supposed to be the PID, but it's not. And I was thinking, how would the filer ever know what the PID is anyway. Well, maybe the client is supposed to hand it over, but Linux doesn't.
Sure enough, breaking out wireshark I see that the NLM v4 LOCK packet hands over a filehandle and a "svid" that matches the number I see.
NLM V4 LOCK Call FH:0x38c878f6 svid:34846 pos:0-0
========a400b02a:005d6abd NLM[jumpy,34846]: 0:0 1 GRANTED (0x796f8ef8)
So the answer is that the number I see isn't magical, and I need to find something on the Linux client side that might tell me how it maps to a process. :-(
Thanks for the help!