[OpenAFS-devel] cmdebug weirdness

[Alf Wachsmann]

Using "cmdebug" from OpenAFS-1.2.5 against a Linux AFS client machine
running OpenAFS-1.2.5 I get weird output for the
"IP address (in hex) of the server holding the callback promise"
(this is from http://www.transarc.ibm.com/Support/afs/debug/cmdebug.html).

Some of the entries are plain "callback 00000000".

The ones actually containing something don't make sense.

Here is a typical example against my own desktop machine (using "-long"):

** Cache entry @ 0xc89a7a48 for 1.536937473.7.4
    2048 bytes  DV 2 refcnt 1
    callback c4fdcea0   expires 1025032524
    0 opens     0 writers
    normal file
    states (0x5), stat'd, read-only

The volume ID 536937473 is indeed a local RO volume. Using "calcinode"
I get a valid inode number that corresponds in this example to a real
directory.

The server holding the callback is "c4fdcea0" which translates to
196.253.206.160. This is not a valid IP address for any of our
fileservers.

I get similar nonsense if I use Transarc's "cmdebug" and a Solaris machine
running Transarc's AFS client.

Any ideas?

Thanks,
          Alf.

-----------------------------------------------------------------------
  Alf Wachsmann                       | e-mail: alfw@slac.stanford.edu
  SLAC Computing Service              | Phone:  +1-650-926-4802
  2575 Sand Hill Road, M/S 97         | FAX:    +1-650-926-3329
  Menlo Park, CA 94025, USA           | Office: Bldg. 50/323
-----------------------------------------------------------------------
                http://www.slac.stanford.edu/~alfw (PGP)
-----------------------------------------------------------------------