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

decremented. Since the newly created file was not marked with the directory quota ID, it was
never was accounted for. As a result, a reduction in quota usage was shown post replication.
The fix was to mark the replica created with the quota ID same as that of the original file, so any
data written into this file is accounted for against the set quota ID.
• Data tiering could result in zero length files.
• When a snapshot was taken, files could be deleted from the source directory.
• Stack overflows were occurring, as a result of some of the IBRIX commands, such as ibrix_fs
requiring a large buffer. The fix lessened the risk of a stack overflow.
• Dangling dentries were created when mv and cp commands were killed during the file creation
operation.
• The upgrade60.sh upgrade script was sometimes showing an invalid file system message in
environments where clusters were on a flat network.
• A delay would occur between serial sequential file writes, about 2 to 20+ seconds between the
first file transfer and the next. This delay would be seen during the drag and drop of multiple 4
GB or larger files from Windows Explorer onto the IBRIX SMB share.
• Checksum errors were being reported while accessing multiple database files from SUSE Linux
NFS Clients, which were reading multiple database pages (8 KB) into the NFS Client memory for
a SAP application. Although some of the data inside the 8 KB page was missing, when the same
page was re-read, the page data was completely intact and the checksum was correct. This
situation only occurred when the read operations involved a cluster network hop to a remote FSN
on a remote couplet, and the issue has been resolved.
• During a mkdir operation, the xdr_encode_netobj dereferencing NULL
xdr_netobj->data pointer message was displayed. The underlying issue has been resolved
so the message no longer appears.
• During Directory Change Notification (DCN) processing, a serialization issue could cause the
thread to loop forever while traversing the list of consumers of the notification. The Linux kernel
would subsequently detect a soft lockup and log messages in regards to the situation would appear
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 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
8 Fixes