User's Manual

hp StorageWorks File System Extender User Guide 213
Recall problems
Description Recall jobs do not continue if an FSE medium is marked unusable during the job.
Explanation If several recalls are waiting for the same resource (medium), which in the meantime has been
marked as unusable, all recall jobs associated to this medium will permanently wait for
resources. This is because required FSE media for recall jobs are determined before the
resource allocation is requested. The recall job is unaware of changes in a particular medium
state if it should become unusable during this process.
Workaround You must abort all recall jobs that are waiting for the damaged (unusable) medium. If an
additional copy of the damaged medium exists, then the recall job uses it instead of the
damaged one the next time it is started.
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 75.