6.2.2 HP IBRIX 9000 Storage Release Notes (AW549-96061, January 2013)
and both the source and destination segments contain the file and its replica. To resolve this issue,
add another segment and restart the evacuation process.
Express Query Database
• If you use hard links, be aware that there could be some inconsistencies 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, such as the last modified time, all hard links on the file system will
show the updated system metadata on the file system as expected. In this example, the "stat"
command will show the correct last modified time for all hard links to the same file, since it shows
metadata as stored on the file system. However, only the hard link you modified will have its
system metadata updated in the Express Query database. The metadata stored in Express Query
for all other hard links to the same file will not show an updated last modified time in this example.
Express Query will treat all hard links as if they are separate files.
To find all hard linked files in a directory tree, enter the following command:
find <path> -links +1 -xtype f
Soft links, also known as symbolic links, do not have the these inconsistencies with the metadata.
Soft links are treated as "normal" paths by Metabox. Metadata for the soft link is maintained
independently of the target of the link. System metadata for the soft link is independent of the
system metadata of the target. Custom metadata is also independent. You can assign custom
metadata to a soft link that differs from the custom metadata assigned to the target of the link.
• The following Express Query audit event types are not yet audited when data validation scans
start and end, even when enabled.
◦ val_scan_started
◦ val_scan_ended
The audit event types are in place to support this functionality in the future.
• In the StoreAll REST API, the system::tier attribute is populated correctly when the file is first
created, or when it is first added to the metadata database if Express Query is enabled on an
existing file system. However, when the file system is moved to another tier by IBRIX file migration
utilities such as data tiering or rebalancer, that change does not yet update the system::tier
attribute available for query through the REST API.
• Root segment evacuation fails on a file system that has express query and retention enabled.
Before running segment evacuation, disable Express Query by entering the ibrix_archiving
–S command. You can re-enable Express Query after segment evacuation completes. To enable
Express Query, enter the ibrix_archiving –s command.
• In certain cases where files created by MDExport or ibrix_audit_reports are very large, in the
millions of files range, the MDImport tool cannot successfully import the files. To allow the files to
be imported, break up the output files into smaller files, on row (line) boundaries, and use the
MDImport tool to import each of the files.
Management console
• If you need to make cluster configuration changes such as adding, extending, or deleting a file
system, be sure that at least two file serving nodes in the cluster are UP and are not in nofmfailover
mode. If a configuration change is necessary and only one node is UP, save a copy of /usr/
local/ibrix/tmp/fmbackup.zip after each configuration change is completed. In the case
where only one node is UP, this copy can be used later if that node goes down before any of the
other nodes come up. In general, before you bring up cluster nodes that have been down for
some time, ensure that the cluster already has an active Fusion Manager running.
• When the active management console is moved to nofmfailover mode, a passive management
console will transition to active mode. Be sure that this transition is complete before you move the
12 Workarounds