5.5.265 HP StorageWorks X9000 Series Release Notes

• 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
nl
DOMAIN\username or a MACHINE\username. On X9000 systems, local users are displayed
as LOCAL\username, and it may seem like you should specify LOCAL\username in the Add
dialog box in Windows. However, in this case, the Windows client cannot interpret LOCAL.
Instead, specify the machine name of the server. For example, to add LOCAL\user1 to an ACL
on a CIFS file shared out by serverX, specify serverX\user1 in the Add dialog box on the
security tab. If you later use the Windows security tab to look at this ACL, the server name will
have been replaced by LOCAL (the CIFS server performs this remapping to ensure that local users
are symmetric between all servers in the cluster, and are not specific to any one machine name
in the cluster).
• The management console GUI or CLI cannot be used to alter the permissions for CIFS shares
created or managed with Microsoft Windows Share Management. The permissions for these
shares are marked as “externally managed” on the GUI and CLI.
• If Robocopy is in use on a client while a file serving node is failed over or failed back, the
application repeatedly retries to access the file and reports the error The process cannot
access the file because it is being used by another process. These errors
10 Fixes