6.2.4 HP StoreAll Storage Release Notes (AW549-96071, April 2013)

◦ Failed node crash capture management. Failed Node iLO Crash Management enables
customer to collect the core dump of the failed node (Segment Server) when Fusion Manager
initiates the failover. This functionality is not enabled by default.
◦ Troubleshooting Guide enhancements
• Manageability
Scheduling for antivirus scans◦
◦ New or revised wizards:
– Expansion wizard
– High availability wizard
– Quota management wizard
– Rebalancing wizard
– Segment evacuation wizard
– Data tiering wizard
– Replication wizard and health checks
Implementation changes in the 6.2.1 release
The following implementation changes occurred with hardware monitoring:
• During an upgrade, user must now run the Firmware Management Tool and perform a set of
manual steps to update the firmware.
• All of the logical (volumes) and physical (controllers, ports, drive enclosures, drives, etc.) objects
that are under the control of a storage controller or pair of storage controllers are grouped together
within a new logical STORAGE_CLUSTER component in the storage health report to describe their
relationship in the storage topology.
• On the 9320 Storage platform, the HA_STORAGE health monitoring category has been replaced
with the new STORAGE_CLUSTER category for monitoring couplet visible storage. The
HA_STORAGE category is still supported but is being deprecated in the next release.
• A subset of all visible storage clusters can be monitored by specifying a list of storage cluster
UUIDs on the hpspmon command line. Prior to this change all storage clusters would have been
monitored.
File systems are created in 64-mode by default
Prior to StoreAll 6.1, file systems were created by default with 32-bit compatibility mode
enabled. Starting in 6.1 the default behavior has changed and compatibility mode is now disabled.
StoreAll creates file systems in 64-bit mode unless you changed the compatibility mode when creating
the file system. However, if the original file system was created with 32-bit compatibility mode enabled
and you later upgrade to 6.1 or later and then extend the StoreAll file system, new segments will be
formatted into the file system as 64-bit mode segments.
The 32-bit compatibility limits the number of inodes on any newly formatted segments to be 32-bit
addressable based on the segbits (number of bits allocated to inodes and segment numbers). If you
have a 32-bit client operating system and 32-bit applications, the 32-bit compatibility mode should
be enabled.
The following output shows the relevant portion of the output from the ibrix_fs -f fsname -i,
indicating how newer segments (65,863,680) appear on a file system originally created with
compatibility mode enabled.
6 Enhancements in the 6.2.4 release