5.5.4 HP X9000 Series Release Notes (TA768-96054, September 2011)

CIFS
• CIFS and X9000 Windows clients cannot be used together because of incompatible AD user to
UID mapping. You can use either CIFS or X9000 Windows clients, but not both at the same time.
• The permissions on the directory exporting a CIFS share govern the access rights that are given
to the Everyone user as well as to the owner and group of the share. Consequently, the Everyone
user may have more access rights than necessary. The administrator should set ACLs on the CIFS
share to ensure that users have only the appropriate access rights. Alternatively, permissions can
be set more restrictively on the directory exporting the CIFS share.
• Occasionally a share cannot be mounted using the DNS name. The workaround is to use the IP
address instead.
• The X9000 CIFS server does not support connections from Linux SMB clients. The workaround is
to use NFS for Linux.
• If any AD user is set to UID 0 in Active Directory, you will not be able to connect to CIFS shares
and errors will be reported. Be sure to assign a UID other than 0 to your AD users.
• Alternate Data Streams (ADS) are not supported. When a file with an ADS is moved or copied
to the CIFS Server, X9000 Software moves/copies the file, but the attached ADS is not copied.
Attempts to create an ADS or a filename containing a colon (:) will be failed by the CIFS Server.
Some older versions of the CIFS Server allowed these ADS files to be saved as separate files with
a colon (:) in their names, such as testfile.htm:Zone.Identifier or
Thumbs.db:encryptable:$DATA. These ADS files are no longer attached to their original
files and can be safely removed if they are not needed. Because the colon (:) is now illegal in a
filename, any ADS files from old CIFS Server versions must be removed from the Linux command
prompt instead of over a CIFS share. (Attempting to delete them using CIFS will fail because of
the illegal filename.)
• When the Microsoft Windows Share Management interface is used to add a CIFS share, the
share path must include the X9000 file system name. The Browse button on the MMC cannot be
used to locate the file system. Instead, enter the entire path, such as C:\data\.
• The X9000 management console GUI and CLI allow only X9000 file systems and directories to
be exported as CIFS shares. However, the Microsoft Windows Share Management interface
allows you to create a CIFS share that is not on an X9000 file system. Although the share will be
available from the file serving node to which Windows Share Management was connected, it
will not be propagated to the other file serving nodes in the cluster.
• Certain special characters do not work in share names. When creating a CIFS share using the
management console GUI/CLI or the Microsoft Windows Share Management interface, do not
include any of the following special characters in the share name:
' & ( [ { $ ` , / \
If a share name contains any of these special characters, the share might not be set up properly
on all nodes in the cluster.
• Certain special characters do not work in share descriptions. When creating a CIFS share using
the management console GUI/CLI or the Microsoft Windows Share Management interface, do
not include any of the following special characters in the share description:
* % + & `
If a description contains any of these special characters, the description might not propagate
correctly to all nodes in the cluster.
• The ibrix_localusers -i <user information> command fails if the user information
includes commas. To enter commas in the user information, use the management console GUI
instead of the CLI.
• When you use the Windows security tab to add local users or groups to a security ACL on a CIFS
file (for either file or share-level permissions), you typically specify the user to add as either a
12 Fixes