On Fri, Sep 03, 2010 at 02:54:08PM -0400, Payne, Rich wrote:
Is there some other meaning that would help me track down on the client the owner (or past owner) of the lock?
Should be the PID of the process running on 10.44.128.20.
Doesn't seem to fit. This is a linux machine, and PID 3 is almost always [migration]. I can't think of why that would be involved in a lock.
Here's the full list I have for this client:
lock status -h ======== NLM host 10.44.128.20 3 0x002c613d:0x00bbfd88 0:0 1 GRANTED (0xffffff08d37bfe00) 13 0x002c613d:0x00bbfd8a 0:0 1 GRANTED (0xffffff08d2a04e00) 46 0x002c613d:0x00bbfd8a 0:0 1 GRANTED (0xffffff0725f07038) 98 0x002c613d:0x00bbfd8a 0:0 1 GRANTED (0xffffff08d2bcac08) 8 0x002c613d:0x018ced8e 0:0 1 GRANTED (0xffffff0813d10230) 48697 0x002c613d:0x00000067 0:0 1 GWAITING (0xffffff08d2a04230) 48696 0x002c613d:0x00000067 0:0 1 GRANTED (0xffffff08372f1620) 42038 0x002c613d:0x00760cb9 0:0 1 GWAITING (0xffffff08d29dda10) 42037 0x002c613d:0x00760cb9 0:0 1 GWAITING (0xffffff08d29ddc08) 41650 0x002c613d:0x00760cb9 0:0 1 GWAITING (0xffffff0583a73c08) 41648 0x002c613d:0x00760cb9 0:0 1 GRANTED (0xffffff08d3686428) 41594 0x002c613d:0x018ced82 0:0 1 GWAITING (0xffffff08d36c5c08) 41593 0x002c613d:0x018ced82 0:0 1 GWAITING (0xffffff08d37baa10) 41592 0x002c613d:0x018ced82 0:0 1 GWAITING (0xffffff08d3636818) 41590 0x002c613d:0x018ced82 0:0 1 GRANTED (0xffffff08d2aecc08) 35517 0x002c613d:0x018ced82 0:0 1 GRANTED (0xffffff08d2ae2428) 29148 0x002c613d:0x018ced82 0:0 1 GRANTED (0xffffff08d36c5818) 21727 0x002c613d:0x000af324 0:0 1 GRANTED (0xffffff08d2a04038)
When I turn the hex inodes into file paths, they're exactly the paths I expect to be locked. But the numbers on the left mean nothing to me. I don't have any processes on this machine in 40K range. In fact my current max PID is 20442, and I don't think it's wrapped over.
Looking through 'netstat', the client only has one line with reference to the filer, and that's the established (TCP) NFSv3 connection.
Although I didn't think it was client port, I'm starting to think that it is, but that the port isn't persistent so there's nothing to find after the fact.