5.6.4 HP StoreAll Storage Release Notes (AW549-96075, June 2013)

• When the Microsoft Windows Share Management interface is used to add a CIFS/SMB share,
the share path must include the StoreAll 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 StoreAll management console GUI and CLI allow only StoreAll file systems and directories to
be exported as CIFS/SMB shares. However, the Microsoft Windows Share Management interface
allows you to create a CIFS/SMB share that is not on a StoreAll 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 a
CIFS/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 StoreAll 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/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 CIFS/SMB 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.)
• When joining a CIFS/SMB domain, the $ character cannot be used in passwords unless it is
escaped with a slash (\) and enclosed in single quotes (' '). For example:
ibrix_auth -n IB.LAB -A john -P 'password1\$like'
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.
• After the initial creation of a snapshot, it can take 4 to 6 minutes to mount the snapshot.
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
ID>-<FS-ID>.info (for example, Rebalance_29-ibfs1.info). Following is an example
of the log file:
070390:0518545 | <INFO> | 3075611536 | collect counters from segment 3
070391:0520272 | <INFO> | 3075611536 | segment 3 not migrated chunks 1
<this line shows the segment has 1 chunk>
070391:0520285 | <INFO> | 3075611536 | segment 3 not migrated replicas 0 070391:
16 Workarounds