Guardian Procedure Errors and Messages Manual

Recovery Use PUP or SMFIXUP to operate on SMF catalog files.
5010 (%11622) An error occurred during SMF lock manager
processing. (device type: 3.36, 25.0, or
52.0)
Cause The NonStop Storage Management Foundation (SMF) internal lock manager encountered
an error (for example, a lock was not obtained because of a problem with a particular file).
Effect The requested operation is not performed.
Recovery Appropriate recovery varies according to the specific cause of the error. In some cases
you can wait and retry the request. The event log contains detailed information that can help you
determine the appropriate action.
5011 (%11623) An error occurred during access of
the ANT table. (device type: 3.36)
Cause A file-system request (create, open, purge, rename, alter, or information inquiry) was made
that required a read or update of the NonStop Storage Management Foundation (SMF) ANT file,
which stores the logical file names and their mappings. A file-system error occurred during the
read or update of the ANT file.
Effect The requested operation is not performed.
Recovery Appropriate recovery varies according to the file-system error that occurred during access
of the ANT file. See the event log to determine the file-system error and take appropriate action.
5012 (%11624) An error occurred during access of
the PENDOPS table. (device type: 3.36,
25.0, or 52.0)
Cause A file-system request (create, purge, rename, or alter) was made, or a file recovery operation
was occurring, that required access to the NonStop Storage Management Foundation (SMF)
PENDOPS (pending operations) file. A file-system error occurred during access of the PENDOPS
file.
Effect The requested operation is not performed.
Recovery Appropriate recovery varies according to the file-system error that occurred during access
of the PENDOPS file. See the event log to determine the file-system error and take appropriate
action.
5013 (%11625) The name range for a physical volume
is exhausted. (device type: 3.36)
Cause A request was made to create a new NonStop Storage Management Foundation (SMF)
logical file, but there are no file names available on the physical volume. In most cases, file names
are not available because the virtual disk process has lost communication with the pool process.
This error can occur either when you specify a physical volume or when you do not specify a
physical volume and this volume is the last one to be tried. In the latter case, other volumes might
have been tried and rejected either because they returned errors or because they were unsuitable
(for example, because they did not match the file's criteria for auditing or mirroring).
Effect The requested operation is not performed.
Error Code Descriptions 83