6.1.4 HP IBRIX X9000 Storage Release Notes

original file is deleted post replication, the directory quota accounted for it gets decremented.
Since the newly created file was not marked with the directory quota ID, it was never 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.
• Stack overflows were occurring, as a result of some of some of the IBRIX commands, such as
ibrix_fs requiring a large buffer. The fix lessened the risk of a stack overflow.
• 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 CIFS 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 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.
• Very high Java CPU consumption caused the active Fusion Manager to become unusable. This
issue has been resolved.
• Users were unable to add segments and extend the file system when it was in compatibility mode.
This 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.
• Servers becoming unresponsive during connection/delegation recovery. The problem occurred
during connection/delegation recovery on servers especially within a large IBRIX cluster.
• The IBRIX client was unable to transfer files until the server they were attached to failed over and
back.
• An [IopIrpCompleteInternal()ioirp.c:316] ASSERTION FAILED message was
displayed when an I/O request packet (IRP) is being added to the queue.
• The upgrade60.sh upgrade script was sometimes showing an invalid filesystem message in
environments where clusters were on a flat network.
• The root file system was constantly running out of space. This release provides the option, -l, for
placing log files in an alternative location for the ibrix_fsck -p 1 and ibrix_fsck -p 2
commands. Use the -l option to prevent the root file system from running out of space. For
example:
ibrix_fsck -p 1 -l /home/user/
ibrix_fsck -p 2 -l /home/user/
In these examples, /home/user/ is the alternative location.
Fixes 9