6.2.1 HP IBRIX 9000 Storage Release Notes (TA768-96074, December 2012)

• System User login credentials are backed up and restored during upgrades. However, any user
data is not retained. Users must save and restore their individual data manually during an upgrade.
• If clients previously mapped an SMB share using the hostname/FQDN, they will be prompted
continuously to enter their credentials when attempting to access the SMB share after the upgrade.
(The share can be accessed successfully using the IP address.) To workaround this situation, disjoin
and then rejoin all file serving nodes to the Active Directory domain. This can be done using the
GUI or the ibrix_auth command.
• The 10Gb NIC driver is updated during the IBRIX v6.2.X software upgrade. However, the new
driver is not utilized/loaded until the server had been rebooted. If you run the upgrade firmware
tool (hpsp_fmt) before you reboot the server, the tool detects that the old driver is still being
used.
• After an upgrade, the following message might appear:
The IbrixArchiving rpm is not installed.
If you see this error message shortly after any online or offline upgrade, returned by any IBRIX
CLI command, restart the active Fusion Manager with the following series of commands on the
active FM server:
1. Enter the following command to set all instances of Fusion Manager to the nofmfailover mode:
ibrix_fm -m nofmfailover -A
2. To restart Fusion Manager, enter the following command:
service ibrix_fusionmanager restart
3. Enter the following command to set all instances of Fusion Manager to the passive mode:
ibrix_fm -m passive -A
Reenter the command or redo the steps in the GUI that previously gave the error message.
NOTE: If the action was to create a file system, then delete the filesystem and recreate it after
restarting the Fusion Manager.
• Use of IBRIX Native clients for any SUSE or SLES kernel is not supported for file systems with
Express Query enabled.
• After upgrading to 6.2.1, the segment evacuation task might fail with the message Completed
with error. This could occur in a rare situation when the file system only has two segments
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 experience long delays (approximately 10 minutes) followed by an HTTP status code in the
5XX range while using the StoreAll REST API, the database back-end of Express Query might not
be able to not set up its server connection end points successfully. Verify the file /etc/hosts is
valid (host names and IP address, paying special attention to “localhost” configuration or any
malformed line) and then restart the cluster node.
• 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
Workarounds 11