User's Manual

HP StorageWorks File System Extender Software user guide 263
Recall problems
Description Device problem is reported after a failed recall. The error message logged in the
fse-hsm_ProcessID.log file is the following:
Linux specific
device busy
Windows specific
31: A device attached to the system is not functioning.
Explanation See Workaround.
Workaround Try to identify the problem as follows:
• Determine the status of the corresponding FSE partition with the command:
fsepartition --status PartitionName
• Check if the fse-hsm process is running on the corresponding FSE client.
Linux specific
Use the ps -ef | grep fse-hsm command for this purpose.
Windows specific
Use Windows Task Manager for this purpose.
If the partition status is set to any other value than mounted, and the fse-hsm process is
running on the client, the problem may be caused by an improper configuration of the
omniORB.cfg files. For information on which omniORB.cfg settings are correct and how to
configure omniORB.cfg appropriately, see ”Reconfiguring FSE interprocess communication”
on page 83.
Description Recall job does not search for alternative copies if the FSE medium is marked 'unusable' after it
has been allocated for recall.
Explanation This may happen in the following situation:
• A running FSE recall job has determined from which FSE medium the data will be recalled
but is still waiting for that medium to become available (probably because another FSE job
has allocated the same medium).
• During this waiting time, the medium status is set to unusable but the recall job that is
waiting is not notified of this change.
The recall job will continue to wait for the medium to become “good” (usable) again, and
therefore it will not search for available redundant copies migrated to other FSE media pools, if
any exist.
Workaround Using the fsejob command, identify and terminate all FSE recall jobs that are waiting for the
unusable FSE medium to become “good” (usable).
If there are redundant copies of the migrated data in other FSE media pools, the subsequent
FSE recall jobs will allocate an FSE medium from one of those pools, and recall the data from it.