User Response: Audit the indicated volume with FIX=NO to verify that the file is
damaged. The audit will reset the file status if the file is found to be undamaged
during the audit. If the file is part of an aggregate, the audit will reset the aggregate
status if the entire aggregate is found to be undamaged. If this volume is in a
primary storage pool that has previously been backed up to a copy storage pool,
attempt to restore damaged files by using the RESTORE STGPOOLcommand.
ANR1163W Offsite volume volume name still contains files which could not be moved.
Explanation: During processing of a MOVE DATAcommand or reclamation, the
server determined that the indicated offsite volume contained one or more files that
could not be moved. One or more files could not be copied from the other available
volumes.
SystemAction: None.
User Response: Check for messages indicating reasons why files could not be
moved. Tocomplete the move operation, you have several options:
Bring the volume back on site and reissue a MOVE DATAcommand to reclaim
the volume.
Make the primary volumes available and reissue a MOVE DATAcommand to
reclaim the volume.
Delete the files by using the DELETE VOLUME command.
ANR1165E Data-integrity error detected for file in storage poolstorage pool name: Node
node name, Typefile type, File space filespace name, File name file name.
Explanation: The server has detected a data-integrity error for the indicated file.
SystemAction: The file will be marked damaged in the server database, and will
not be accessed for future operations. If this file is part of an aggregate, the entire
aggregate will be marked damaged. If a usable copy of the file exists in another
storage pool, that copy may be accessed for future operations involving the file.
User Response: If the indicated storage pool is a primary pool, and a usable copy
of the file exists in a copy storage pool, you can recreate the file in the primary
pool using the RESTORE STGPOOLcommand. If the indicated storage pool is a
copy storage pool, it is possible that the primary copy of the file is usable, but was
not accessed because the access mode for the primary storage pool or volume is
unavailable. If this is the case, the primary copy of the file may be made accessible
by changing the access mode of the primary pool or volume.
188
Version 3 Release 7