>> I'm trying to get AFS running on a 220, but so far to no avail. I can
>> get afsd running, and I can look around in the /afs tree, but when I
>> try to run a program from /afs... the machine crashes nine times out
>> of ten (at least).
>> I think that trouble comes when afsd is trying to transfer the program
>> from the server to the cache.
I experience the same problem. I have also tried copying an afs file and
this also crashes the machine (sometimes). 0c9 or 0c4 appear on the 220's
leds.
I am running AFS 3.2beta.
By the way, how can I get a list of what files are currently cached ?
cmdebug <server> -long produces:
** Cache entry @ 0x01d66b80 for 1.536871389.290.2180
3900 bytes DV 1 refcnt 0
callback 00000000 expires 713536204
0 opens 0 writers
normal file
states (0x1), stat'd
et al.
This presumably refers to a cached file. How can I translate
the number in the first line to a pathname (relative to the
volume) ?
Also, can I do a non-server specific cmdebug ?
Mike
