Explanation
A recall was aborted from HSM. The ERRNO set from HSM explains why the recall was aborted.
Transient errors (The operation must be retried after the associated problem was solved):
ENOSPC : No space left on device. HSM couldn't free space for the recall.
ENOMEM : Not enough memory available to acquire the required resocurces for the recall.
ESRCH : The internal communication between master and distributor failed.
EACCES : Most common errno. One of the failures below:
- The recall daemon are exiting. System cleanup ongoing.
- Recovery of previously failed nodes is ongoing.
- File is immutable and can't be opened for write / truncate.
- The HSM internal processing failed due to issues with the DMAPI.
EBUSY : HSM can't acquire exclusive rights on the file.
EFAULT : The system detected an invalid address in attempting to use an argument.
EINTR : The DMAPI implementation allows interruption and the process was interrupted.
EINVAL : The requested right is not valid or the session or token is not valid or token was DM_NO_TOKEN.
Static errors (The operation can't be fullfilled. Recall not possible):
EIO : The stub file is orphan.
ENOENT : The file doesn't exist in the file system.
EBADF : The file handle does not refer to an existing or accessible object.
System action
The recall request was aborted from the HSM service.
User response
Transient errors:
Solve problem indicated from the errno.
On GPFS platforms: Use command dsmmigfs q -d -n=all to verify HSM and GPFS are running properly.
Retry the recall operation if failed file can be identified.
Enable HSM Logging if failed failed file cannot be identified and wait for new occurrence.
(HSM Logging allows you to map between the token displayed from the FMV message and the recalled file)
Static errors:
Restore the file from backup.