We are having an issue on 2 linux servers that we think may be related to locking. Lock status shows many locks that are GWAITING, like so:

NLM[crater.pp.bcinfra.net,13260]: 94691143974912:18446649382565576704 1 GRANTED (0xffffff02c3600e00)

NLM[carlsbad.pp.bcinfra.net,679]: 71133248356352:18446672940461195264 1 GWAITING (0xffffff02aa227428)

NLM[carlsbad.pp.bcinfra.net,682]: 71107478552576:18446672966230999040 1 GWAITING (0xffffff0423515230)

NLM[carlsbad.pp.bcinfra.net,684]: 71171903062016:18446672901806489600 1 GWAITING (0xffffff04cfccaa10)

NLM[carlsbad.pp.bcinfra.net,685]: 71167608094720:18446672906101456896 1 GWAITING (0xffffff03bc421818)

NLM[carlsbad.pp.bcinfra.net,687]: 71159018160128:18446672914691391488 1 GWAITING (0xffffff049a4a5e00)

NLM[carlsbad.pp.bcinfra.net,689]: 71116068487168:18446672957641064448 1 GWAITING (0xffffff02a966d038)

NLM[carlsbad.pp.bcinfra.net,693]: 71047349010432:18446673026360541184 1 GWAITING (0xffffff0332284620)

We are thinking we may be running into the same issue as this person:

http://comments.gmane.org/gmane.linux.nfs/42929

but we are already doing NFS over TCP.

I believe that the hex looking number from lock status (ie 0xffffff0332284620) is possibly an inode. Anyone know if that's true? If so, how can I take that and get an actual file name?

Thanks,

Dan