6.3.2 HP StoreAll OS Release Notes

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
command times out while waiting for a response from the storage. Although the deletion was
successful the command reports it as failed and StoreAll preserves the associated volume group
(ivg) and logical volume (ilv). This issue has been observed on the HP StoreAll 9730.
To resolve this issue, rerun the logical volume delete command using the “-X” override option, for
example: ibrix_lv -d -s <ilv#> —X
The override option forces the removal of the StoreAll Logical Volume record from the StoreAll
database.
• When using the ibrix_vs -a command during file system extension, the command fails on a
combined cluster configuration (such as 9730 and 9320) with the following error message:
Lun already set for physical volume dxx can two vendorstorages see the
same luns?
Contact HP Support for assistance.
• You might not be able to mount a file system after an unmount if you:
Stop Express Query:
ibrix_archiving -S
1.
2. Evacuate the segment.
Workarounds 27