Table of Contents
Advertisement
StoreAll client auto-startup interferes with debugging
The StoreAll client is set to start automatically, which can interfere with debugging a Windows
StoreAll client problem. To prevent this, reboot the machine in safe mode and change the Windows
StoreAll client service mode to manual, which enables you to reboot without starting the client.
1.
Open the Services control manager (Control Panel > Administrative Tools > Services).
2.
Right-click StoreAll client Services and select Properties.
3.
Change the startup type to Manual, and then click OK.
4.
Debug the client problem. When finished, switch the Windows StoreAll client service back to
automatic startup at boot time by repeating these steps and changing the startup type to
Automatic.
Synchronizing information on file serving nodes and the configuration
database
To maintain access to a file system, file serving nodes must have current information about the file
system. HP recommends that you execute ibrix_health on a regular basis to monitor the health
of this information. If the information becomes outdated on a file serving node, execute ibrix_dbck
-o to resynchronize the server's information with the configuration database. For information on
ibrix_health, see
NOTE:
The ibrix_dbck command should be used only under the direction of HP Support.
To run a health check on a file serving node, use the following command:
ibrix_health -i -h HOSTLIST
If the last line of the output reports Passed, the file system information on the file serving node
and Fusion Manager is consistent.
To repair file serving node information, use the following command:
ibrix_dbck -o -f FSNAME [-h HOSTLIST]
To repair information on all file serving nodes, omit the -h HOSTLIST argument.
Troubleshooting an Express Query Manual Intervention Failure (MIF)
An Express Query Manual Intervention Failure (MIF) is a critical error that occurs during Express
Query execution. These are failures Express Query cannot recover from automatically. After an
MIF occurrence, Express Query stops processing journal events and serving queries for the file
system. Although journal event processing has stopped, file system activity continues to be journaled
and stored for later processing, when the database has recovered from the MIF state. Although
these errors inhibit the normal functionality of Express Query, they are typically due to another
unrelated event in the cluster or the file system. Therefore, most of the work to recover from an
Express Query MIF is to check the health of the cluster and the file system and take corrective
actions to fix the issues caused by these events. Once the cluster and file system have an OK status,
the MIF status can be cleared. Once the MIF status is cleared, Express Query services for the file
system are automatically restarted and a database recovery process is attempted.
In some very rare cases, a database corruption might occur as a result of these external events or
from some internal dysfunction. Express Query attempts to recover the database from redundant
data stored specifically for such cases. However, Express Query might be unable to recover from
an internal database corruption. Such situations are identified when clearing the MIF state (as
described in the following procedure) results in the database entering the MIF state again.
NOTE:
When a file system is in the MIF state, Express Query event recording is still occurring.
When the database is re-enabled, the recorded events are processed and the database is
synchronized with the file system again.
To recover from an Express Query Manual Intervention Failure (MIF):
"Monitoring cluster health" (page
Synchronizing information on file serving nodes and the configuration database 127
86).
Advertisement
Table of Contents
Troubleshooting
