| GRAND.CENTRAL.ORG |
|---|
This is a table of admin tools vos error codes, contained in the 'AV' error table. A maximum of 256 codes are available in this table. In addition to this table, this data is also available in the form of a com_err error table. The error code values are also available in a C header file.
| Code | Value | Name | Message |
|---|---|---|---|
| 0 | 22016 | ADMVOSSERVERNULL | the volume server parameter cannot be NULL |
| 1 | 22017 | ADMVOSCELLHANDLENULL | the cell handle parameter cannot be NULL |
| 2 | 22018 | ADMVOSCELLHANDLEBADMAGIC | the cell handle parameter failed to pass the magic number test. Most likely the cell handle is invalid, or has been overwritten by mistake. |
| 3 | 22019 | ADMVOSCELLHANDLEINVALID | the cell handle parameter is marked as invalid. |
| 4 | 22020 | ADMVOSCELLHANDLEINVALIDVOS | the cell handle parameter is marked as invalid for volume server requests. |
| 5 | 22021 | ADMVOSCELLHANDLENOAFSTOKENS | the cell handle does not contain valid AFS tokens. |
| 6 | 22022 | ADMVOSMUSTBERWVOL | the volume identifier parameter must be a read write volume in order to make a backup volume. |
| 7 | 22023 | ADMVOSBACKUPVOLWRONGSERVER | a backup volume already exists for volume identifier, but it exists on a server different from the one that holds volumeidentifier. |
| 8 | 22024 | ADMVOSSERVERHANDLENULL | the server handle parameter cannot be NULL |
| 9 | 22025 | ADMVOSSERVERHANDLEINVALID | the server handle parameter is marked as invalid |
| 10 | 22026 | ADMVOSSERVERHANDLEBADMAGIC | the server handle parameter failed the magic number test. Most likely the server handle is invalid, or has been overwritten by mistake. |
| 11 | 22027 | ADMVOSSERVERNOCONNECTION | a connection with the server could not be established. |
| 12 | 22028 | ADMVOSPARTITIONPNULL | the partition parameter cannot be NULL |
| 13 | 22029 | ADMVOSPARTITIONTOOLARGE | the partition parameter is too large |
| 14 | 22030 | ADMVOSVOLUMENAMETOOLONG | the volume name parameter is too long |
| 15 | 22031 | ADMVOSVOLUMENAMENULL | the volume name parameter cannot be NULL |
| 16 | 22032 | ADMVOSVOLUMENAMEINVALID | the volume name parameter cannot end with .readonly or .backup |
| 17 | 22033 | ADMVOSVOLUMEID | the volume identifier parameter cannot be NULL |
| 18 | 22034 | ADMVOSVOLUMEIDTOOBIG | the volume identifier parameter cannot exceed VOLMAXPARTS |
| 19 | 22035 | ADMVOSVOLUMENOEXIST | the volume identifier does not exist on the specified server and partition |
| 20 | 22036 | ADMVOSVOLUMENAMEDUP | the volume name is already in use. |
| 21 | 22037 | ADMVOSPARTITIONNAMENULL | the partition name parameter cannot be NULL |
| 22 | 22038 | ADMVOSPARTITIONNAMEINVALID | the partition name parameter must start with /vicep |
| 23 | 22039 | ADMVOSPARTITIONNAMETOOLONG | the partition name parameter is too long. |
| 24 | 22040 | ADMVOSPARTITIONNAMETOOSHORT | the partition name parameter is too short. |
| 25 | 22041 | ADMVOSPARTITIONNAMENOTLOWER | the partition name parameter must be all lower case letters. |
| 26 | 22042 | ADMVOSPARTITIONIDNULL | the partition identifier parameter cannot be NULL |
| 27 | 22043 | ADMVOSPARTITIONIDTOOLARGE | the resulting partition identifier exceeds VOLMAXPARTS |
| 28 | 22044 | ADMVOSEXCLUDEREQUIRESPREFIX | the volume prefix parameter cannot be NULL when the exclude prefix is VOS_EXCLUDE |
| 29 | 22045 | ADMVOSSERVERADDRESSPNULL | the server address parameter cannot be NULL |
| 30 | 22046 | ADMVOSSERVERENTRYPNULL | the server entry parameter cannot be NULL |
| 31 | 22047 | ADMVOSSERVERTRANSACTIONSTATUSPNULL | the server transaction status parameter cannot be NULL |
| 32 | 22048 | ADMVOSVLDBENTRYNULL | the vldb entry parameter cannot be NULL |
| 33 | 22049 | ADMVOSVLDBDELETEALLNULL | at least one of the arguments must not be null - server handle, partition, volume identifier. |
| 34 | 22050 | ADMVOSNEWVOLUMENAMENULL | the new volume name parameter cannot be NULL |
| 35 | 22051 | ADMVOSSERVERANDPARTITION | both the server handle and the paritiion parameters must be specified. |
| 36 | 22052 | ADMVOSDUMPFILENULL | the dump file parameter cannot be NULL |
| 37 | 22053 | ADMVOSDUMPFILEWRITEFAIL | an error occurred while trying to write more data to the dump file |
| 38 | 22054 | ADMVOSDUMPFILEOPENFAIL | an error occurred while trying to open dump file |
| 39 | 22055 | ADMVOSRESTOREVOLEXIST | the volume to be restored exists on a server different from the one specified and you specified an incremental restore. If you wish to restore this volume, specify a full restore. |
| 40 | 22056 | ADMVOSRESTOREFILEOPENFAIL | an error occurred while trying open restore file |
| 41 | 22057 | ADMVOSRESTOREFILECLOSEFAIL | an error occurred while trying close restore file |
| 42 | 22058 | ADMVOSRESTOREFILEREADFAIL | an error occurred while trying read the restore file |
| 43 | 22059 | ADMVOSRESTOREFILEWRITEFAIL | an error occurred while trying send the contents of the restore file |
| 44 | 22060 | ADMVOSRESTOREVOLUMENAMETOOBIG | the volume name is too big |
| 45 | 22061 | ADMVOSVOLUMENAMEANDVOLUMEIDNULL | either the volume name or the volume identifier parameter must not be NULL |
| 46 | 22062 | ADMVOSVOLUMEPNULL | the volume parameter cannot be NULL |
| 47 | 22063 | ADMVOSVOLUMEMOVERWONLY | only read write volumes can be moved |
| 48 | 22064 | ADMVOSVOLUMERELEASERWONLY | only read write volumes can be released |
| 49 | 22065 | ADMVOSVOLUMENOREPLICAS | only replicated volumes can be released |
| 50 | 22066 | ADMVOSVOLUMENOREADWRITE | unable to create a backup volume because no read write volume exists |
| 51 | 22067 | ADMVOSVLDBBADENTRY | unable to create a backup volume because the vldb entry is invalid |
| 52 | 22068 | ADMVOSVLDBBADSERVER | unable to get server's address from vldb |
| 53 | 22069 | ADMVOSVLDBDIFFERENTADDR | skipping volume since read write is in a different location |
| 54 | 22070 | ADMVOSVLDBNOENTRIES | there were no entries in the vldb retrieved. |
XXX text to be written XXX
XXX text to be written XXX