Guardian Procedure Errors and Messages Manual

Recovery If you specified a physical volume, retry the request either without specifying a physical
volume or specifying a different physical volume. If you did not specify a physical volume, start
the pool process (if it's not running), wait, and retry the request.
5014 (%11626) No physical volumes are available.
(device type: 3.36)
Cause A request was made to create a new NonStop Storage Management Foundation (SMF)
logical file but there are no physical volumes available for one of the following reasons:
• Either there are no physical volumes in the storage pool that the virtual disk process is
associated with, or none of the physical volumes in the pool is in the UP state, or none of the
physical volumes in the pool matches the pool's criteria (for example, a pool might require
that physical volumes be mirrored, but currently all the physical volume mirrors are in the
DOWN state).
• None of the physical volumes in the storage pool matches the criteria specified for the file.
For example, the file might be audited but none of the physical volumes in the pool are currently
able to generate audit.
• You specified a physical volume on which to create the file, but that physical volume either is
not part of the pool that the virtual disk process is associated with or it is subject to one of the
problems described in the preceding bullets.
Effect The requested operation is not performed.
Recovery Appropriate recovery varies according to the specific cause of the problem. See the
event log to determine appropriate action. The recovery might be, for example, to add physical
volumes to the storage pool, bring volumes to the UP state, or remove the physical volume
specification from the original request.
5015 (%11627) The outcome for the requestis unknown.
(device type: 3.36, 25.0, or 52.0)
Cause During processing of a file-system request (create, purge, rename, or alter) the NonStop
Storage Management Foundation (SMF) subsystem lost communication with the disk process. This
might occur, for example, as a result of a processor failure.
Effect The requested operation is not performed.
Recovery Take appropriate action to recover the disk process and then retry the request.
5017 (%11631) Unable to read one of the SMF catalog
tables. (device type: 3.36, 25.0, or 52.0)
Cause A process other than the NonStop Storage Management Foundation (SMF) subsystem
attempted to directly access an SMF catalog file and a file-system error occurred.
Effect The requested operation is not performed.
Recovery See the event log for detailed information and take appropriate action.
5018 (%11632) An error occurred during message processing.
(device type: 3.36, 25.0, or 52.0)
Cause A file-system request (create, purge, or alter) was made against a NonStop Storage
Management Foundation (SMF) object, and the reply from the disk process contained an error.
This often indicates a HP internal error.
Effect The requested operation is not performed.
84 File-System Errors