6.2.2 HP IBRIX 9000 Storage Release Notes (AW549-96061, January 2013)

Enter the following command on one line to kill the specific coordinator processHung Task
/usr/local/ibrix/bin/migrator_daemon --serviceid=4100 --port=9174 -f
ifs2 --logflag=6 -L /usr/local/ibrix//log/ -j Migrator_58-ifs2-worker1
/usr/local/ibrix/bin/purge_coordinator --serviceid=5379 --port=9173
-D -y -f ifs2 -L /usr/local/ibrix//log/ -j SnapReclamation_59-ifs2
SnapReclamation
/usr/local/ibrix/bin/validation_coord --serviceid=6147
--port=9173/usr/local/ibrix/bin/validator --jobid=60 --fsname=ifs1
--path=/ifs1 --scantype=1
DataValidation
/usr/local/ibrix/bin/dir_tree_case_insensitive -p -j 51CaseInsensitive
3. Restart the CUD by entering the following command:
/usr/local/ibrix/bin/ibrix_cud restart
SMB
• SMB and IBRIX 9000 Windows clients cannot be used together because of incompatible AD user
to UID mapping. You can use either SMB or IBRIX 9000 Windows clients, but not both at the
same time on the cluster.
• The IBRIX 9000 SMB server does not support connections from Linux SMB clients. The workaround
is to use NFS for Linux.
• SMB DCN is supported on Windows File Explorer with the following exception:
◦ The recursive notification flag in the notify request is ignored. Notifications are delivered only
for one directory level.
• If SMB is joined to a domain before introducing LDAP ID mapping or changing the domain or
the provision mode, you should clear the name cache on each node. This step prevents unexpected
results such as the corruption of a name cache entry when the new configuration is in place. To
clear the cache, run the following command:
/opt/likewise/bin/lw-lsa ad-cache --delete-all
• When the Microsoft Windows Share Management interface is used to add a SMB share, the
share path must include the IBRIX 9000 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 IBRIX 9000 management console GUI and CLI allow only 9000 file systems and directories
to be exported as SMB shares. However, the Microsoft Windows Share Management interface
allows you to create an SMB share that is not on an IBRIX 9000 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.
• 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 an
SMB file (for either file or share-level permissions), you typically specify the user to add as either
a DOMAIN\username or a MACHINE\username. On IBRIX 9000 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 an SMB 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 SMB server performs this remapping to ensure that
16 Workarounds