During migration, a file is encountered that was previously found to be damaged. If this file is part of an aggregate, the entire aggregate was previously marked damaged, possibly because an integrity error was detected for some other file within the aggregate.
The damaged file will not be moved.
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, you can also attempt to restore damaged files by using the RESTORE STGPOOL command.