No Subject

Anonymous Anonymous
Sun Jan 2 06:12:35 CET 2000


Could not make fetch-status call: Unknown error: -1 (-1)
multi-sending wakeup: seq = 3567, error = -1
proc_msg: byte = 36
Rec message: opcode = 4 (getnode), size = 292

It seems that while looking up utah.edu under /afs, the lkm generated
the first error.

Mar 24 02:03:41 eecs582c /kernel: xfs_lock
Mar 24 02:03:42 eecs582c /kernel: xfs_lookup: (uni-mannheim.de, 15)
Mar 24 02:03:42 eecs582c /kernel: xfs_inactive, 0xf4111e80
Mar 24 02:03:42 eecs582c /kernel: xfs_lookup error: 0
Mar 24 02:03:42 eecs582c /kernel: xfs_lookup() error = 0
Mar 24 02:03:42 eecs582c /kernel: xfs_unlock
Mar 24 02:03:42 eecs582c /kernel: xfs_getattr
Mar 24 02:03:42 eecs582c /kernel: xfs_unlock
Mar 24 02:03:42 eecs582c /kernel: xfs_inactive, 0xf4111e80
Mar 24 02:03:42 eecs582c /kernel: xfs_lock
Mar 24 02:03:42 eecs582c /kernel: xfs_lookup: (utah.edu, 8)
Mar 24 02:03:56 eecs582c /kernel: xfs_lookup error: -1
Mar 24 02:03:56 eecs582c /kernel: xfs_lookup() error = -1
Mar 24 02:03:56 eecs582c /kernel: xfs_unlock

I could not do anything under /afs, but normal unix file system commands
work fine.

I traced the error to the RXAFS_FetchStatus in arlad/fcache.c, but
strangely enough, I can not find the definition of this function.
It looks like a RPC call so I guess its definition will be generated
by a stub generator when arla gets compiled.  Is that correct?

Thanks,

Cheng 


------------------------------------------
Say who you are, but know who you are not.






More information about the Arla-drinkers mailing list