6.3 HP StoreAll Storage Release Notes (TA768-96086, April 2013)

Windows Client
• If the StoreAll Windows Client is registered with Fusion Manager already, clicking on Start Service
After registration under the Registration tab displays a Response Code =400 error. Click the
Recover Registration option instead.
General
• A crash might occur if there is a change in ownership of the file while a quota is being enabled.
There are plans to provide a fix in a future release.
• The output from the ibdircheck command might show incorrect statistics counters. For some
conditions the number of errors does not match the number of corrections. There are plans to fix
this issue in a subsequent patch. If you encounter this issue, contact HP support for analysis of the
ibdircheck logs to determine if you have a benign situation or if you have any file system errors
truly left uncorrected.
• After the files are archived, evacuation might fail and you might see an RO lock error message
when you attempt to access the files from the second node.
To resolve this issue:
1. Unload the CommVault driver from all nodes on hosts that control segments for this file system.
2. Run segment evacuation. See the HP StoreAll Administrator Guide for your platform for
additional information.
3. Reload the CommVault driver. Refer to the CommVault documentation for additional
information.
• HP recommends that you do not run rebalancer, segment evacuation and/or data tiering tasks
with ibdirecheck.
• Any object store user can get a container listing for any object store user on an object mode REST
API share. Permission changes are not allowed on the account level directory.
To prevent a user other than the account owner from seeing any containers, change the directory
permission (chmod) of the account directory to 700 after the directory has been created. The
account directory is created after the account owning user creates their first container. This
permission change also prevents other users from reading or writing objects in any containers,
even if you grant such permission to the containers via the API.
For example, after the first container creation for user2 whose UID is 3002, if the object store
share’s directory path is /objModeFS/objStore, the /objModeFS/objStore/3002 account
directory will be created with 777 permission, giving full read, write, and execute permission to
all users. Changing permission to 700 removes all permissions for all other users, for both container
listings and object access within containers.
To grant other users in the same group read and/or write permission to objects in any containers,
turn on the group execute bit, for the account directory. Then, change the permissions of the
containers to which you wish to grant access via the API’s Set Container Permission request. If
you also want those group users to be able to list containers, then also turn on the group read
bit. Similarly for other users outside the group, turn on the world execute bit to allow object access,
and turn on the world read bit to enable container listings.
• The ibrix_pv -a -o mpath command does not recognize a multipath device. The command
works properly when an argument is added to ignore the standard SCSI devices. Execute the
command as follows, specifying the path to your device.
ibrix_pv -a -o accept:/dev/mapper/mpath10,~standard
• The ibrix_lv -d -s <range of Segments> command sometimes displays a “failed
command” message. Although the segments for which the command fails are still listed by the
ibrix_lv -l command, they are successfully removed from the underlying Operating System
LVM view. This issue is a timing condition for large file system delete operations where the delete
20 Workarounds