Status Codes
When the NLDS is asked to PUT or GET some data, the transaction goes through a
number of states from initialisation to completion.
The state of a transaction can be queried by using the nlds stat
command
in the nlds_client
.
Transaction states
Value |
State |
Description |
---|---|---|
|
|
Transaction is starting. |
|
|
Transaction is in the message queue. |
|
|
Transaction is being split into smaller transactions. The user doesn’t have to worry about this. |
|
|
Scanning the files and directories in the PUT transaction. |
|
|
Recording the scanned files into the catalog entry for the transaction. |
|
|
Putting the files to the NLDS. Actually transferring the data. |
|
|
Get a catalog entry. |
|
|
Getting the files from the NLDS tape store. |
|
|
Getting the files from the NLDS object store cache. |
|
|
Transfer transaction is starting. |
|
|
Archive transaction is starting. |
|
|
Putting the aggregated files into the tape store from the NLDS cache. |
|
|
Requesting the files from the tape system when they have to be fetched from tape. |
|
|
Remove from the catalog any inaccessible files in the transaction. |
|
|
Updating the catalog with post object store write |
|
|
Updating the catalog with post tape write information. |
|
|
Remove from the catalog any empty storage locations. This occurs if a write to tape or restore to object store fails. |
|
|
Transaction has completed successfully. |
|
|
Transaction has failed completely. |
|
|
Transaction has completed but with some errors. |
|
|
Transaction has completed but with some warnings. |
|
|
NLDS is searching for the state of a request. The user should not see this state! |