User's Manual

164 Monitoring and maintaining FSE
Example excerpt from the FSE error log file
From this excerpt, the following information can be acquired:
• The manual recall process has been started on the FSE client fse_client.company.com on the
HSM file system mounted to the directory /mnt/fsefs01.
• Four files from the same directory were specified for recall.
• The parameter JobID has zero value. This indicates that no recall job has been created for these
files, since none of them had a usable copy at the moment when the fsefile command was
invoked.
Example excerpt from the FSE event log file
From this excerpt, the following information can be acquired:
• The manual recall process with process ID 027749. invoked on the FSE client fse_client, failed,
because no usable copies of the files were available.
For location of log files, see appendix ”Directory layout”.
Managing FSE recall jobs
The efficient recall process creates one FSE recall job for each FSE medium from which files will be
recalled. In order to abort the recall process, you need to abort each particular recall job that was created
for it. Similarly, you cannot change the overall recall priority, but you can increase or decrease priority of a
single recall job at a time.
For details on monitoring FSE jobs, see section ”Monitoring FSE jobs” on page 157. For details on
changing FSE job priority and aborting FSE jobs, see description of the fsejob command in the FSE CLI
reference.
Retrieving detailed information
You can retrieve information related to configured FSE resources, files on HSM file systems, and FSE jobs
using either FSE command-line interface (CLI) or the FSE Management Console.
NOTE: If you cannot find specific information using the FSE Management Console, try using FSE CLI
instead. With certain FSE resources, FSE CLI enables retrieval of additional and more detailed information.
Furthermore, files and older file generations on a particular HSM file system cannot be monitored with FSE
Management Console.
[E HSM(/mnt/fsefs01) ,001030.3042864048 2005/08/26 12:51:32.296;
root@fse_client.company.com; i_HSM_i::EfficientRecall, i_hsm_impl.cpp,v 6.9 :705]
Recall failed. JobID: 0. HSM Job Idx: 0Files have not a usable copy.
Inode FileID Path relative to mount point
0x17bca3e000044002 30 dir1/1/fn__1
0x17bca3e100044003 31 dir1/1/fn__2
0x17bca3e200044004 32 dir1/1/fn__3
0x17bca3e300044005 33 dir1/1/fn__4
Execution stack dump:
00000001. i_HSM_i::EfficientRecall i_hsm_impl.cpp,v 6.9:705
End of stack dump.
[2005/08/25 12:57:15, fse_client, 027749, RMG, , 0, ] WARNING: No usable (marked
good or unreliable) media found for recall!