It was this that had me thinking it was the inode:

http://www.gossamer-threads.com/lists/netapp/toasters/10863

The 3rd post in there says that he was able to turn the hex into inode numbers and then get a file path from that.

From: Bennett Todd <bet@rahul.net>
To: Dan Finn <dan_j_finn@yahoo.com>
Sent: Thursday, September 6, 2012 4:26 PM
Subject: Re: Getting actual file paths from lock status

I wouldn't expect inum there, but something that encodes the device and inum together, where device uniquely identifies the volume across all on your net. Maybe a GUUID-like construct. Maybe the inum is some easily recognised subset of the bits.

If you can find the inum and the filesystem it belongs to, the path might come from find(1) -inum