Guardian Procedure Errors and Messages Manual
Recovery See the event log for additional information and take action as appropriate. Bring the
SMF process to the DOWN state and then to the UP state. Retry the request. If the problem persists,
contact your service provider.
5072 (%11720) Recovery processing was unable to initialize PENDOPS
processing. (device type: 3.36, 25.0, or 52.0)
Cause When a NonStop Storage Management Foundation (SMF) process attempted to perform
recovery processing after the failure of a create, purge, rename, or update of an SMF object, an
error occurred that prevented the SMF process from initializing the PENDOPS (pending operations)
file. This error can also be returned if there is a lock failure during recovery processing or if the
PENDOPS file is unavailable.
Effect The requested operation failed and recovery processing is aborted. The SMF process enters
the DOWN state.
Recovery See the event log for detailed information. In the case of a lock failure, take appropriate
action. Otherwise, wait and retry the operation by bringing the SMF process to an UP state. If the
problem persists, contact your service provider.
5073 (%11721) A PENDOPS semaphore failed; the process that locked
a SMF object could not be identified.
(device type: 3.36, 25.0, or 52.0)
Cause When a NonStop Storage Management Foundation (SMF) process attempted to perform
recovery processing after the failure of a create, purge, rename, or update of an SMF object, an
error occurred in the PENDOPS (pending operations) file, which prevented identification of the
process that locked an SMF object.
Effect The requested operation failed and recovery processing is aborted. The SMF process enters
the DOWN state.
Recovery Wait and retry the operation by bringing the SMF process to an UP state. If the problem
persists, contact your service provider.
5076 (%11724) An invalid operation code was found in the
PENDOPS table; the PENDOPS entry is invalid.
(device type: 3.36, 25.0, or 52.0)
Cause When the NonStop Storage Management Foundation (SMF) subsystem attempted to perform
recovery processing after an SMF process failed, an invalid operation code was found in the
PENDOPS (pending operations) file.
Effect The requested operation failed and recovery processing is aborted.
Recovery Contact your service provider.
5313 (%12301) A virtual disk process encountered an error when
trying to perform the requested operation.
(device type: 3.36)
Cause During processing of a file-system request (create, open, purge, rename, alter, or information
inquiry) on a NonStop Storage Management Foundation (SMF) logical file, the virtual disk process
encountered an error.
Effect The requested operation is not performed.
Recovery Appropriate recovery varies according to the specific error. See the event log to determine
the specific file-system error and take appropriate action.
Error Code Descriptions 87