6.1.4 HP IBRIX X9000 Storage Release Notes

Fixes in the 6.1.2 release
Resolution for a critical potential security issue. Refer to the Security Bulletin available at:
https://h20566.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?
docId=emr_na-c03510876
The CIFS shadow copy feature that was disabled in the 6.1.1 release has been renabled by
default in the 6.1.2 release. For more information about the feature, see the HP IBRIX X9000
Network Storage System File System User Guide.
When FTP was configured to allow NAT settings, the pasv_promiscuous=YES parameter
needed to be written to the vsftpd configuration file.
NFS client access would hang when the network temporarily lost its TCP connection.
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.
When segments reached 70-80% of capacity, the Windows client server took too long to access
the cluster, causing applications to fail.
When nodes were rebooted or a file system was mounted or unmounted, files and folders that
were moved, renamed, or deleted on the file system were also deleted on snapshots that existed
before the unmount or reboot.
After the cluster is upgraded to 6.1.2, all future snapshots are protected from these deletions.
However, at least one snapshot should be taken of all snapshots that existed before the upgrade
to protect objects from being deleted.
Dangling dentries were created when mv and cp commands were killed during the file creation
operation.
CIFS shares could not be accessed and the cluster node reported the error
STATUS_INSUFF_SERVER_RESOURCES.
When a CRR job was stopped, it could be restarted incorrectly after a failover.
Data tiering could result in zero length files.
The error init_special_inode: bogus i_mode(0) was reported when applications created
and deleted files repeatedly, causing issues with the application.
When power was removed from a server, it did not fail over.
Fixes in the 6.1.1 release
The ibrix_fs_ops -f FSNAME option did not work correctly.
A new option, ibrix_crr -K, is now available to forcefully stop a remote replication task. A
CRR task in any state can be stopped with this option. The task will be removed from the active
and inactive task lists.
When a local user or group was deleted, the user or group was not deleted from the CIFS
database.
When a CIFS client did not close a file gracefully, the files in the CIFS share were locked.
The NFS automount script did not work with user VIFs. The automount capability, including the
ibrix_autoconnect command, is obsolete and has been retired.
An attempt to create a file over RPC succeeded, but the file did not exist.
A delay occurred when mounting a segment if there were a large number of orphan inodes.
An lwiod failure caused the CIFS service to stop.
When attempting to add ACLs on files and folders in a CIFS share, local users were not visible.
10 Fixes