5.5.5 HP IBRIX X9000 Release Notes

Corrected in 5.5.257
The following fixes were made in this release:
• When a file was uploaded into an FTP share, the file was owned by ftp:ftp, not by the user
who uploaded the file. Files uploaded to an FTP share are now owned by the logged-in user.
• When a file was uploaded into an HTTP share, the file was owned by daemon:daemon, not by
the user who uploaded the file. Files uploaded to an HTTP share are now owned by the user
doing the upload.
• Performance was slow when using Windows Explorer to list files on CIFS shares with large numbers
of files.
• CIFS shares could not be browsed using IP addresses or Round Robin names.
• When a directory tree quota was removed, multiple errors such as err ibrix_quotamonitor:
failed to find Name for dirtree_id=2 were logged in /var/log/messages.
• When a user was added with the ibrix_localusers command, the new user was not added
to nodes running the passive management console.
• A CIFS issue prevented file serving nodes from joining a child domain.
• Restrictions for segment evacuation were corrected in the system administrator guides.
Corrected in 5.5.232
The following fixes were made in this release:
Configuration
• When an attempt was made to create a CIFS share using the same name as an existing share,
the X9000 Software did not report the error, and instead deleted the existing share and created
the new share.
• The ibrix_clusterconfig command did not set up NTP correctly.
• The ibrix_nic command could create a duplicate user VIF on a node hosting a passive agile
management console.
• The GUI allowed an invalid host tuning option to be set.
Remote replication
• Running the X9000 Software snapshot feature on a file system that was a replica target for
continuous remote replication could result in snapshot errors if the target was the root of the file
system.
• Subsequent remote replication jobs (run-once or continuous) started on the same source file system
to the same target file system did not sync all objects that were deleted on the source between
replications.
• Rapid combinations of creates, deletes, or renames using the same file names sometimes were
not replicated correctly.
• Running two or more replication tasks that were replicating to different subdirectories of the same
target cluster and file system did not always work well in previous releases if any of the parallel
replication tasks were Continuous.
Quotas
• When quotas were checked on a file system, errors were reported for file serving nodes that had
not mounted the file system.
• Server operations slowed when users exceeded their quotas.
8 Fixes