6.0.1 HP IBRIX X9000 Release Notes

Fixes in the 6.0.1 release (build 6.0.340)
The following fixes were made in this release:
• The correct creation time was not maintained when a file on a CIFS share was modified or moved.
Now, when a file is moved or modified, the original creation time is preserved as a file property
visible to the client.
• It was possible to create two directories with the same name, but differing in case, if one of the
names used characters from the Latin-1 character set. Users were then unable to save or retrieve
files from one of the directories.
• When a CIFS client did not close a file gracefully, the files in the CIFS share were locked.
• When a local user or group was deleted, the user or group was not deleted from the CIFS
database.
• CIFS users in extended ACLs were incorrectly given permissions that should be applied only to
the owner of the file.
• Run-once remote replications did not replicate files correctly when the source or destination
directory name included spaces.
• The defaults for the TcpKeepalive parameters on the CIFS server did not match the defaults on
Windows servers.
• An @ symbol could not be used in a file or directory name.
• When the active management console failed over, ibrix_event did not send the correct email
notifications.
• An lwiod failure caused the CIFS service to stop.
• If a directory name ended with the @ symbol, the contents of the directory could not be read when
it was restored from a snapshot.
• The CIFS server did not handle requests properly when filenames had leading backslashes.
• When attempting to add ACLs on files and folders in a CIFS share, local users were not visible.
You can now add local users; however, the cluster or client should be in the domain.
• NDMP backups failed when used with the VLS 9200.
• An attempt to create a file over RPC succeeded, but the file did not exist.
• When a user quota setting was changed, the ibrix_edquota -l command reported the error
RealQuotaMonitor - directory tree quota has unparsable output.
• A race condition caused a rebalance operation to fail with the message
ASSERT[deleg->dlg_side == idel_ds] failed: Trying to send downgrade
delegation to local or remote delegation.
• When a segment becomes unavailable, that state persists after remounting the filesystem or
migrating the unavailable segment. The segment unavailable state must now be explicitly cleared.
The following message appears after a segment unavailable alert:
Filesystem includes one or more unavailable (or read-only) segments.
Recommendation: verify storage health and contact customer support to run FSCK.
To proceed with mounting segment as unavailable (or read-only), use force option.
8 Fixes in the 6.0.1 release (build 6.0.340)