5.
Sometimes cluster and file system health checks have an
OK
status but Express Query is yet in
a
MIF
condition for one or several specific file systems. This unlikely situation occurs when
some data has been corrupted and it cannot be recovered.
To solve this situation:
a.
If there is a full backup of the file system involved, do a restore.
b.
If there is no full backup:
1.
Disable Express Query for the file system, by entering the following command:
ibrix_fs -T -D -f <FSNAME>
2.
Delete the current database for the file system by entering the following command:
rm -rf <FS_MOUNTPOINT>/.archiving/database
3.
Enable Express Query for the file system by entering the following command:
ibrix_fs -T -E -f <FSNAME>
NOTE:
The moment Express Query is enabled, database repopulation starts for
the file system specified by
<FSNAME>
.
4.
If there are any backup of the Custom Metadata with the tool MDExport, re-import
them with MDImport as described in CLI Reference Guide.
NOTE:
If no such backup exists, the custom metadata must be manually created
again.
5.
Wait for the resynchronizer to complete by entering the following command:
ibrix_archiving -l
Repeat this command until it displays the
OK
status for the file system.
6.
If none of the above worked, contact HP.
Troubleshooting an Express Query Manual Intervention Failure (MIF)
153