5.5.5 HP IBRIX X9000 Release Notes

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
occur for 15 to 20 minutes. The client's copy will then continue without error if the retry timeout
has not expired. To work around this situation, take one of these steps:
◦ Stop and restart the Likewise process on the affected file serving node:
# /opt/likewise/bin/lwsm stop lwreg && /etc/init.d/lwsmd stop
# /etc/init.d/lwsmd start && /opt/likewise/bin/lwsm start srvsvc
◦ Power down the file serving node before failing it over, and do failback operations only
during off hours.
The following xcopy and robocopy options are recommended for copying files from a client
to a highly available CIFS server:
xcopy: include the option /C; in general, /S /I /Y /C are good baseline options.
robocopy: include the option /ZB; in general, /S /E /COPYALL /ZB are good baseline
options.
• If a node failback occurs while xcopy or robocopy is copying files to a CIFS share, the copy
operation might be interrupted and need to be restarted.
Fixes 13