Segment Full Alert: Using Ibrix_Rebalance to Resolve a Segment 90% Full Alert

5 n1mwpseg01 ilv5 4096 257902212 42455516 41849264 16768000
16557536 83 n1mwpseg02 No No MIXED No
6 n1mwpseg02 ilv6 4096 253902212 207194060 206556556
32768000 32677672 18 n1mwpseg01 No No MIXED No
7 n1mwpseg03 ilv21 4096 257902212 168471596 167865344
16768000 16665277 34 n1mwpseg04 No No MIXED No
8 n1mwpseg04 ilv22 4096 257902212 167436520 166830268
16768000 16663241 35 n1mwpseg03 No No MIXED No
Rebalance Job#1 results summary:
Ok that looks good for segments 5 , 1 and 3. Now that we have a good buffer, let’s go
ahead and kick off the standard rebalance job so that we can get all 8 segments in the File
System at or around 62% USED.
From you FM run:
#/usr/local/ibrix/bin/ibrix_rebalance -r -f <fs_name> -c
Just as you did on the last rebalance when the %USED on all segments is equal to 62%
you may stop the job just as before and you will be done.
Final synopsis:
After the general rebalance run, all segments for the FS are now well balanced at 62-63%
per seg. USED.
SEGMENT OWNER LVNAME BLOCKSIZE BLOCKS(1k) BFREE(1k) BAVAIL(1k)
FILES FFREE USED% BACKUP ONBACKUP?
1 n1mwpseg01 ilv1 4096 257902212 95521292 94915040 16768000 16594941 62
n1mwpseg02 No No MIXED No
2 n1mwpseg02 ilv2 4096 257902212 95535068 94928816 16768000 16592122 62
n1mwpseg01 No No MIXED No
3 n1mwpseg03 ilv3 4096 257902212 95333268 94727016 16768000 16595416 63
n1mwpseg04 No No MIXED No
4 n1mwpseg04 ilv4 4096 257902212 95367616 94761364 16768000 16584138 63
n1mwpseg03 No No MIXED No
5 n1mwpseg01 ilv5 4096 257902212 96371700 95765448 16768000 16597932 62
n1mwpseg02 No No MIXED No
6 n1mwpseg02 ilv6 4096 253902212 93953720 93316216 32768000 32577481 62
n1mwpseg01 No No MIXED No
7 n1mwpseg03 ilv21 4096 257902212 95265476 94659224 16768000 16584235 63
n1mwpseg04 No No MIXED No
8 n1mwpseg04 ilv22 4096 257902212 95403076 94796824 16768000 16597865 63
n1mwpseg03 No No MIXED No