Mike Gahan <[EMAIL PROTECTED]> writes:
> Also, can I do a non-server specific cmdebug ?
[lws] cmdebug -help
Usage: cmdebug -servers <server machine> [-port <IP port>] [-long ] [-help ]
The use of "server" in this context is very misleading. The
client/server model used in the implementation of cmdebug has bubbled
up into the user interface. (I consider this a UI bug) Here, "server"
means a machine running an AFS cache manager, which implements the
server side of the debug RPC, and listens on port 7001. IT DOES NOT
mean "file server" or "volume location server" or any such thing. I
apologize for the confusion.
>** Cache entry @ 0x01d66b80 for 1.536871389.290.2180
> ...
>This presumably refers to a cached file. How can I translate
>the number in the first line to a pathname (relative to the
>volume) ?
The format of these FIDs is Cell.Volume.Vnode.Uniquifier.
When you do an "ls -i", the inode number is constructed by shifting
the volume ID up by 16 bits, adding the vnode number, and masking off
the MSb so the resulting number is not negative.
So, if I've done the math right, the inode number for this entry
should be 31260962. From here you've got the standard UNIX question
"How do I get a pathname from this inode number?" which is often
answered by "find . -inum 31260962 -print" (assuming you've changed
directories to the mountpoint of this volume).
Alternatively, you could look for a file of the listed size by doing a
"find . -size 3900 -print", which isn't as conclusive, but avoids doing
the math.
Lyle Transarc 707 Grant Street
412 338 4474 The Gulf Tower Pittsburgh 15219
