User's Manual

180 Monitoring and maintaining FSE
• Run consistency check of the File System Catalog and enable automatic correction. For details, see
Consistency check of FSC vs. FSE media, page 182.
The following mismatches may also result from the above condition.
• suspicious
A file is reported as suspicious when it exists on the HSM file system but does not have a file ID. It is
possible that the FSE implementation is unaware of its existence. Possible causes for this file state are:
• The disk was full when the file was created and the extended file attributes that FSE uses could not
be written.
• The file was created before the platform-native file system was mounted as an HSM file system (for
example, the lost+found directory does not have its file ID).
• A power failure occurred and the file ID was not written or the Hierarchical Storage Manager did
not receive the file system event notification.
• The file is new and the Hierarchical Storage Manager did not get the file system event notification
yet.
• offline file is prolonged or not shortened
Files that have not been released properly or which have not been fully recalled due to an error have
the “prolonged” status. In such cases, the file is in an offline state but still occupies storage space.
To resolve the problem, first recall the file by accessing it, and then release it with the
fsefile --release command.
• mismatch report, such as:
• MigrationID mismatch
• Owner mismatch
• Name mismatch
• Not all attributes in NSC
•Size mismatch
NOTE: FSE implementation is able to trace “suspicious” files and put them under FSE control in time. To
resolve their status at once, use the fsefile --migrate command to put them on the dirty file list. This
way the files are immediately recognized and their attributes are preserved.
For files for which a mismatch in FileSize, FileName or OwnerID is reported, the last file system event
was most probably not reported to the Hierarchical Storage Manager. To resolve such mismatches, use the
fsefile --trigger-migration command to manually migrate the files.
Example results of the FSC vs. HSM file system consistency check
Linux specific
# fsecheck --fsc-hsmfs cosmos
[2003/12/03 14:49:45] Started FSC vs. HSMFS check. Partition cosmos
[2003/12/03 15:06:02] 578684 0 /mnt/fsefs_01/A9/linux-2.4.19-ea/NewFile
Missing in FSC.
[2003/12/03 15:06:49] 154342 273932147200
/mnt/fsefs_01/A9/linux-2.4.19-ea/COPYING
DUMP: FSC HSMFS Notes
MigID 273932147200 273932147200
FileSize 18691 32930 MISMATCH
FileName COPYING COPYING
OwnerID 154336 154336