6.2.2 HP IBRIX 9000 Storage Release Notes (AW549-96061, January 2013)

in the kernel log (BUG: soft lockup – CPU#<X> stuck for 10s!
[i_worker_X:<pid>]). The serialization issue has now been fixed.
• There was a request to document file system mount information (specifically, the change to the
default mount options in 6.1 and the use of ibrix_mountpoint to set mount options). The man
pages for the ibrix_mount and ibrix_mountpoint commands and the HP IBRIX 9000
Storage File System User Guide were updated.
• The Windows IBRIX Client (WIC) would crash when WIC was built in debug mode.
• The following fixes have been made for the 9730 Storage platform:
Storage could become unresponsive when multiple surface scans were launched on a single
physical disk. Interaction between background surface scans and performance has been
significantly improved.
◦
◦ The controller caching policy has been adjusted to significantly reduce the occurrence of
command timeouts and aborts when running heavy workloads with small block sizes.
◦ Drive LEDs could go dark when an MDS600 storage enclosure I/O module was
removed. Drive LEDs are now refreshed in this scenario.
◦ Sometimes MDS600 storage enclosure I/O modules were not visible to the storage controllers
after a FW flash of the I/O module. This has been corrected.
◦ Improved resilience against SAS topology disruptions due to events such as booting of blades,
which could lead to missing paths to storage.
• For a list of firmware fixes, see the HP HPSP_FMT User Guide
• MDS600 and D6000 drive enclosure drawers are now reported by number: Drawer 1 for the
front-facing left drawer and Drawer 2 for the front-facing right drawer.
• A memory leak was occurring in Fusion Manager.
• For a list of fixes in the Storage Provisioning Tool (SPT), see the HP HPSP_SPT User Guide.
The var/log/message file was not getting rotated nightly.
Workarounds
This section contains workarounds for product situations that may occur:
Installation and network configuration
• On 9720 systems with G6 blades, the Quick Restore installation reports that the G6 Ethernet
firmware must be upgraded. The Ethernet device (eth0) must be up when you upgrade the
firmware. Use the following command to bring up eth0 and then upgrade the firmware:
# ifup eth0
The following document provides additional detail for HP Support personnel:
http://saw.cce.hp.com/km/saw/view.do?docId=emr_na-c03466768
• When creating a user NIC with a VLAN tag on a bond, running the ibrix_nic -c command
causes the parent bond to become degraded. The workaround is to determine the device that is
down and then bring up that device manually. For example, if bond0 is made up of eth4 and
eth5, use ifcfg to determine which device is down. Then use ifup to bring up the device,
such as ifup eth4.
Upgrades
• If you plan to do an online upgrade, I/O must be occurring on a user virtual interface (VIF). Online
upgrades are only supported when I/O to shares is exclusively through User VIFs. When a VIF
Workarounds 9