6.2 HP IBRIX 9300/9320 Storage Administrator Guide (AW549-96049, December 2012)
# ./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.
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 the cluster
Use the following procedure to remove a node from the cluster:
1. If the node is hosting a passive Fusion Manager, go to step 2. If the node is hosting the active
Fusion Manager, move the Fusion Manager to nofmfailover node:
ibrix_fm -m nofmfailover
2. On the node hosting the active Fusion Manager, unregister the node to be removed:
ibrix_fm -u server_name
3. Uninstall the IBRIX software from the node.
./ibrixinit -u
This command removes both the file serving node and Fusion Manager software.
The node is no longer in the cluster.
Maintaining networks
Cluster and user network interfaces
IBRIX software supports the following logical network interfaces:
• Cluster network interface. This network interface carries Fusion Manager traffic, traffic between
file serving nodes, and traffic between file serving nodes and clients. A cluster can have only
one cluster interface. For backup purposes, each file serving node can have two cluster NICs.
• User network interface. This network interface carries traffic between file serving nodes and
clients. Multiple user network interfaces are permitted.
100 Maintaining the system