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

0520290 | <INFO> | 3075611536 | segment 3 not migrated files 0
070391:0520294 | <INFO> | 3075611536 | segment 3 not migrated directories 0
070391:0520298 | <INFO> | 3075611536 | segment 3 not migrated root 0
070391:0520302 | <INFO> | 3075611536 | segment 3 chunk: inode inum 300000017
(29B3A23C), poid hi64 300000017 (29B3A23C), primary 500000017 <this line
shows information about the chunk>
Run the inum2name command to identify the symbolic name of the chunk file:
root@centos bin]# ./inum2name --fsname=ibfs 500000017
ibfs:/sliced_dir/file3.bin
After obtaining the name of the file, use a command such as cp to move the file manually. Then
run the segment evacuation process again.
Migration to an agile management console configuration
When a cluster is configured with a dedicated, standard management console, the Quick Restore
installation procedure installs both the Fusion Manager and the File Serving Node packages on the
dedicated, standard management console and on each node of the cluster. If you then attempt to
migrate to an agile management console configuration, the migration procedure will fail. To avoid
the failure, uninstall the StoreAll Server package from the dedicated, standard management console,
and uninstall the StoreAll Fusion Manager package from the file serving nodes. You can then perform
the migration.
Complete the following steps:
1. On the standard management console, check for the IbrixServer RPM:
# rpm qa | grep i IbrixServer
If the RPM is present, the output will be similar to the following:
IbrixServer-<version>
2. If the IbrixServer RPM is present, uninstall the RPM:
# rpm -e IbrixServer-<version>
3. On each file serving node, check for the StoreAll Fusion Manager RPM:
# rpm qa | grep i IbrixFusionManager
If the RPM is present, the output will be similar to the following:
IbrixFusionManager-<version>
4. If the RPM is present on the node, remove the RPM:
# rpm -e IbrixFusionManager-<version>
X9000 clients
CIFS/SMB and StoreAll Windows clients cannot be used together because of incompatible AD
user to UID mapping. You can use either CIFS/SMB or StoreAll Windows clients, but not both at
the same time.
On StoreAll Windows clients, when Active Directory is switched from the static mapping mode
to dynamic mapping, users with Full Control cannot rename files. This situation occurs because
the UIDs and GIDs have changed. Take these actions:
If the static mapping mode had UID 0 and GID 0 mapped to the domain administrators and
you want to retain this configuration, execute the following command:
ibrix_activedirectory -A -d DOMAIN_NAMES -W DEFAULTWINUSERNAME M
U 0 G 0
Change the UID and GID on all existing files and directories to match the new UID and GID.
For example, if user John previously had UID=10 and now has UID=20003456, you will
need to change the owner on all files with UID=10 to UID=20003456.
Workarounds 17