6.3 HP StoreAll 9300/9320 Storage Administrator Guide (AW549-96072, June 2013)

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.
The analyzer log lists the chunks that were left on segments. Following is an example of the
log:
2012-03-13 11:57:35:0332834 | <INFO> | 1090169152 | segment 3 not migrated
chunks 462
2012-03-13 11:57:35:0332855 | <INFO> | 1090169152 | segment 3 not migrated
replicas 0
2012-03-13 11:57:35:0332864 | <INFO> | 1090169152 | segment 3 not migrated
files 0
2012-03-13 11:57:35:0332870 | <INFO> | 1090169152 | segment 3 not migrated
directories 0
2012-03-13 11:57:35:0332875 | <INFO> | 1090169152 | segment 3 not migrated root
0
2012-03-13 11:57:35:0332880 | <INFO> | 1090169152 | segment 3 orphan inodes 0
2012-03-13 11:57:35:0332886 | <INFO> | 1090169152 | segment 3 chunk: inode
3099CC002.8E2124C4, poid 3099CC002.8E2124C4, primary 807F5C010.36B5072B poid
807F5C010.36B5072B
2012-03-13 11:57:35:0332894 | <INFO> | 1090169152 | segment 3 chunk: inode
3099AC007.8E2125A1, poid 3099AC007.8E2125A1, primary 60A1D8024.42966361 poid
60A1D8024.42966361
2012-03-13 11:57:35:0332901 | <INFO> | 1090169152 | segment 3 chunk: inode
3015A4031.C34A99FA, poid 3015A4031.C34A99FA, primary 40830415E.7793564B poid
40830415E.7793564B
2012-03-13 11:57:35:0332908 | <INFO> | 1090169152 | segment 3 chunk: inode
3015A401B.C34A97F8, poid 3015A401B.C34A97F8, primary 4083040D9.77935458 poid
4083040D9.77935458
2012-03-13 11:57:35:0332915 | <INFO> | 1090169152 | segment 3 chunk: inode
3015A4021.C34A994C, poid 3015A4021.C34A994C, primary 4083040FF.7793558E poid
4083040FF.7793558E
Use the inum2name utility to translate the primary inode ID into the file name.
Removing a node from a cluster
In the following procedure, the cluster contains four nodes: FSN1, FSN2, FSN3, and FSN4. FSN4
is the node being removed. The user NIC for FSN4 is bond0:1. The file system name is ibfs1,
which is mounted on /ibfs1 and shared as ibfs1 through NFS and SMB . FSN3 and FSN4 are
the failover pair, and bond0:2 is configured as the stand-by interface.
1. Stop High Availability:
ibrix_server -m –U
2. Verify that the Active Fusion Manager is on a server other than FSN4. Run the following
command from FSN4:
ibrix_fm -i
If the Active Fusion Manager is on FSN4, move the Fusion Manager to nofmfailover mode:
ibrix_fm -m nofmfailover
3. Migrate all segments from FSN4 to its failover partner (FSN3):
ibrix_fs -m -f ibfs1 -h FSN4,FSN3
NOTE: If there is a large number of segments to be migrated and/or segments can be
migrated to several FSNs (in SAN environments), run the following command instead:
ibrix_fs -m -f ibfs1 -s LVLIST -h FSN_name
Removing a node from a cluster 119