6.3.2 HP StoreAll OS Release Notes

• Do not use spaces in share names. The GUI cannot create a share if there is a space in the name.
• SMB clients have a 45 second timeout on every SMB request they make. If a request's timer
expires before a response comes, the client disconnects and terminates the SMB connection with
this error message: The specified network name is no longer available. After
this, the client must reconnect to the SMB server. If you are seeing this message from clients
connected to a busy server, they may be encountering timeouts from overload. For more information
about SMB client timeouts, see http://support.microsoft.com/kb/102067.
LDAP
• When configuring LDAP on the GUI, double quotes are not supported in any fields of the LDAP
configuration window, including the password field. Also, escaped slashes are not supported. If
you enter \\; it will be parsed literally as \\ instead of \. Also, the ibrix_ldapconfig
command supports double quotes only at the beginning and end of a value. For example:
ibrix_ldapconfig -a -h 10.30.239.174 -b "cn=Manager,dc=ldapx,dc=net"
-p "mypassword "
The command does not support escaped slashes.
LDAP ID mapping
• Increasing the values of the LdapMaxWaitTime and LdapMaxEntries can affect the performance
of name resolutions for SMB and non-SMB users in large LDAP directory environments. The AD
name cache protects against excessive LDAP searches. The default value for these parameters is
10. The range of values is 0 (unlimited) or 1–32767.
Block snapshots
• Deleting files while running snapshot reclamation can cause errors to be logged. The impact is
negligible, unless you want to delete the entire snaptree, in which case snaptree deletion will fail.
To workaround this issue, run snapshot reclamation job again.
• Snapshot creation may fail while mounting the snapshot. The snapshot will be created successfully,
but it will not be mounted. Use the following command to mount the snapshot manually:
ibrix_mount -f <snapshotname> -m /<snapshotname>
• Quotas are disabled on block level snapshots (for example, MSA2000 snapshots) and the quota
information from the origin file system is not carried to the block level snap file system. Block level
snapshots are temporary file systems that are not writable. Users should not query quota information
against block level snap file systems.
• After the initial creation of a snapshot, it can take 4 to 6 minutes to mount the snapshot.
Block snapshots are not created when a volume group is mapped to more than one logical volume.
Remote Replication
• The NIC status reported by the CRR health check may be outdated compared to the status reported
by the ibrix_nic –l command. This is due to the CRR health check reporting on stale data.
This issue will be fixed in a future release.
• When data is being copied to the target file system during a remote replication job (either
continuous or run-once), on rare occasions, a synchronization issue may occur while the
domain_scan phase is in progress as part of the replication job. As a result, some files may be
missing from the target file system. To resolve the issue, restart the replication job (note that it is
possible the issue could occur again). This will be fixed in a future StoreAll release.
• Remote replication might fail to transfer Windows Access Control Lists (ACLs) if cross-protocol
ACL synchronization is enabled on the source cluster nodes, but not on the target cluster nodes.
Workarounds 21