HP StoreAll OS 6.5.1 Release Notes

]# echo "MIF: workaround 1G RPC limit exceed. (error code 17)" >
/ifs1/.archiving/database/serialization/ManualInterventionFailure
3. Restart the Express Query daemons by executing the following command:
ibrix_archiving -r
Command output:
Command succeeded!
4. Wait for the file system to enter the MIF state, which you can verify by executing the
ibrix_archiving –l command. When the file system is in the MIF state, the command
output will show the following:
FS NAME STATE
------- -----
ifs1 AbnormalDatabase(MIF)
5. Clear the MIF state by executing the following command:
ibrix_archiving -C ifs1
Command output:
Command succeeded!
6. Wait for the file system to be registered with Express Query, which you can verify by executing
the ibrix_archiving –l command. When Express Query registration has occurred, the
command output will show the following:
FS NAME STATE
------- -----
ifs1 DaemonStarting
7. Once the file system is in the OK (Idle) state, the file system is ready for use. Execute the
following command to verify the file system state:
ibrix_archiving –l
Command output example:
FS NAME STATE
------- -----
ifs1 OK (IDLE)
Be aware that the file renames have not yet been processed; therefore, the path names for
these file will be out of sync. This will be fixed the next time the Online Metadata Synchronizer
task is run.
• When you create a file system that is not enabled for Express Query, the following tasks are
scheduled for the file system: MetadataSynchronizerOperation, SynchronizeOperation, and
ReportsExpirationOperation. These tasks are listed when you execute the ibrix_task -l -s
-f FS_NAME command.
These tasks will not affect the file system in any way and will not consume resources as long as
Express Query is not enabled on the file system.
• If you use hard links, be aware that there could be some unexpected behavior in the metadata
stored in the Express Query database. If you perform any file system operations on a hard link
that changes the system metadata, metadata stored in the file system is updated, and it is visible
to a stat call to any of the links to that file. For example, if hardlinkA and hardlinkB point to the
same file, and hardlinkA is updated, then the stat hardlinkA command produces the same
(updated) size as the stat hardlinkB command, since the stat command shows metadata
from the file system.
In contrast, Express Query treats hard links to the same file as if they are separate files. As a
result, only the hard link you modified has its metadata updated in Express Query. The Express
Query metadata for all other hard links to the same file are not updated. Express Query requests
Workarounds 17