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

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.

Snapshots

• 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.

Segment evacuation

• The segment evacuator cannot evacuate segments in a READONLY or BROKEN state.

• If data is written to a very large file during evacuation of the segment containing the file, the

writing process might experience an I/O error and terminate prematurely.

• The segment evacuation process aborts if a segment contains chunk files; these files have chunks

in more than one segment. You will need to move chunk files manually. The evacuation process

generates a log reporting all chunk files on the segment. The log file is saved in the management

console log directory (the default is /usr/local/ibrix/log) and is named Rebalance_<job

Fixes 13