6.0.2 HP IBRIX X9000 Storage Release Notes (AW549-96044, January 2013)

NOTE: If you need to uninstall only the agile management console packages from a node, retaining
the file serving software packages, use the ibrixinit -tmo option. For example, if the passive
management console is configured incorrectly on a node or has a corrupt fminstance.xml file,
run the following command to uninstall the agile management console RPMs and unregister the passive
agile management console on the node:
ibrix/ibrixinit -tmo -u
Fixes
Fixes in the 6.0.2 release
The following fixes were made in this release:
• The error init_special_inode: bogus i_mode(0) was reported when applications created
and deleted files repeatedly, causing issues with the application.
• CIFS clients running Windows XP Service Pack 3 could not save a file with a Danish character in
the filename.
• When FTP was configured to allow NAT settings, the pasv_promiscuous=YES parameter
needed to be written to the vsftpd configuration file.
• The CIFS service failed when a large number of CIFS clients were connected concurrently for
read/writes.
• When a file system containing a CIFS share was replicated in continuous mode, file deletions
from the CIFS share were not propagated to the target.
• Under certain conditions, slow performance was observed when large directories were accessed
using the CIFS/SMB protocols. The performance has been improved in this release.
• If the quota monitor service could not access a server, the service issued an error and did not
obtain other quota information.
• NFS clients would hang when the network lost TCP connectivity temporarily.
• The "ibrix_auth -t -S <sharename> ..." command was failing with the output
(LW_ERROR_DATA_ERROR). The cached data is incorrect whenever it encountered
an unprovisioned user in Active Directory.
Users can run the "ibrix_auth -t -S <sharename> ..." command successfully.
• Phase 1 of ibrix_fsck did not detect entry died before it was born corruption.
• When segments reached 70–80% of capacity, client were unable to write to a CIFS share.
• When run in corrective mode ibrix_fsck could incorrectly remove a directory from a snapshot
view if the directory was moved to a different parent directory after the snapshot was taken.
• Data tiering could result in zero length files.
• The quota current size would be reduced after running the rebalance task, even though files were
not modified or deleted. During movement of files across segments, there are intermediate replica
files that are created. Once data from an original file is synced with its replica, the original file
is deleted and replica is promoted as the original file. These replicas have to be marked with the
directory quota ID same as that of the original master file, but that was not occurring. As the
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.
• Data tiering could result in zero length files.
8 Fixes