6.2.3 HP StoreAll Storage Release Notes (update)

3. Wait 1 minute for the commands to complete.
4. Place the current Active FM into 'nofmfailover' mode, this will trigger the migration by entering
the following command:
ibrix_fm -m nofmfailover
5. Wait another minute, after which, you should find the Active FM on the desired node. Verify
FM is at the correct node by entering the following command:
ibrix_fm -i
6. From the Active FM, place the rest of the nodes back into Passive mode by entering the
following command:
ibrix_fm -m passive -A
• During an upgrade from 6.1 to 6.2.3, if there is I/O work load on a file serving node, the HP-SMB
services might not start itself after upgrade. This could make the SMB share not accessible from
that node. To recover from this situation, restart the HP-SMB services after upgrade if there is a
share access issue after 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 StoreAll OS 6.2.x software upgrade. However, the
new driver is not utilized/loaded until after the server has 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.
• Use of StoreAll Native clients for any SUSE or SLES kernel is not supported for file systems with
Express Query enabled.
• After upgrading to 6.2.3, 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 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
Workarounds 15