Linux specific
The FSE check log file is named check_hsmfs_fsc_PartitionName.log and located in the directory /var/opt/fse/log.
Windows specific
The FSE check log file is named check_hsmfs_fsc_PartitionName.log and located in the directory %InstallPath%\var\log.
The value of %InstallPath% depends on the choice made in the FSE installation process. It defaults to C:\Program
For each inconsistent file entry, the full file path is reported to the FSE check log.
To start the FSC consistency check using FSE
fsecheck
To start the FSC consistency check using graphical user interface, in the FSE Management Console window, in the object tree,
Figure 35 Running a consistency check of FSC against HSM file system
Types of inconsistencies
Reported inconsistencies in the FSE check log may be the following:
•missing in FSC
A file is reported as missing in FSC when the file ID exists on the HSM file system, but is not recorded in FSC. Probably the file has not been successfully migrated yet.
To resolve the problem, manually put the file on the dirty file list using the command fsefile
•not in NSC
Files are reported as not being recorded in NSC in case the fsc_ns*.lrf files are removed from the File System Catalog directory.
To resolve the problem, do one of the following:
• Run the File System Catalog recovery. For details, see File System Catalog recovery, page 235.
HP StorageWorks File System Extender Software user guide 179