Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2010-02-01 11:05:41 →
Size: 2494
Editor: ReneStandke
Comment:
← Revision 4 as of 2010-02-01 12:29:02 → ⇥
Size: 2394
Editor: ReneStandke
Comment:
Deletions are marked like this. Additions are marked like this.
Line 74: Line 74:

== error message: fs: invalid argument ==
 * Check the Kernelversion and the build AFS Version!

Issues

Missing token is not handled well

$ osd volumes io -lun 1
RX xdr error
Cannot list volumes
Request aborted.

$ osd createv io 1 536870924
Createvolume failed: RXOSD_create_part ended with 13
Request aborted.

In general, missing privileges are an issue but there is no "friendly output" describing the cause of the problem. Some examples of unprivileged access attempts:

fs osd

Error 13 reading length of metadata

works with r privilege granted to system:anyuser

osd read

RX xdr error \\ Cannot read the object \\ rx_EndCall returns: 13 \\ Request aborted.

requires token

osd volumes

RX xdr error \\ Cannot list volumes \\ Request aborted.

requires token

osd examine

RXOSD_examine failed with code 13 \\ Request aborted.

requires token

Database queries osd listosds and osd servers seem to work unauthenticated.

error messages

  • missing admin token, not osd files and other topics 

cd /afs/ifh.de/testsuite/testosd

fs ls arch-test
f rw-nieprask        3162 2009-08-18 14:19:22 arch-test

fs ls testfile1
f rw-  ffrank  1000000000 2009-06-04 13:46:01 testfile1

fs archive arch-test -osd 4
Could not archive arch-test, error code was 22

fs archive testfile1 -osd 4
Could not archive testfile1, error code was 13

fs ls testfile2
o rw-  ffrank  1000000000 2009-06-04 13:55:40 testfile2

fs archive testfile2 -osd 4
Could not archive testfile2, error code was 13

klog admin

fs archive testfile2 -osd 4
testfile2 done

fs archive testfile2
Could not archive testfile2, error code was 2       ERROR!  Should work
  • question: 2 archives of a file, file will be updated, what happened? (see AfsOsd/Archivierung, one archive discarded?)

Vicep-access maybe not active

  • Log on a machine with OSD Kernel
  • with "osd list" you get a list of all osd server

  • "osd statistic <server>" shows the rpc statistic of the server

  • read or write a file on the server - call "osd statistic <server>" again

Little Overview of RPC's:

121 write without Vicep-access

131 read without Vicep-access

  • If there is no 121 or 131, but other RPC's changes vicep is active.

  • If rpc 121 or 131 changes, vicep is not active!

Other rpc's: http://pfanne.rzg.mpg.de/trac/openAFS-OSD/wiki/Specs

AfsOsd/Issues (last edited 2010-02-01 12:29:02 by ReneStandke)