Anil,
man 1m fsadm_vxfs has a section that explains most of fields and values.
In most cases, a smaller number is better.
Important fields to look at are:
Immeds to Add
Dirs to Reduce
Blocks to Reduce
Avg # Extents
%Free in smaller than 64 blocks
%Free in smaller than 8 blocks
I schedule a defrag for all vxfs file systems monthly. To give you an example of what my /var looks like:
Directory Fragmentation Report
Dirs Total Immed Immeds Dirs to Blocks to
Searched Blocks Dirs to Add Reduce Reduce
10052 725 9469 1 8
27
Extent Fragmentation Report
Total Average Average Total
Files File Blks # Extents Free Blks
19342 31 1 1474780
blocks used for indirects: 24
% Free blocks in extents smaller than 64 blks: 2.29
% Free blocks in extents smaller than 8 blks: 0.16
% blks allocated to extents 64 blks or larger: 82.06
HP suggests "%Free blocks in extents smaller than 64 blocks" be less than 50%, your # is approaching that. In most cases you're not going to run a defrag and say "Wow, what an improvement." But even small improvements over time can help out the big picture. Although a defrag can be run at any time, there will be a performance hit while it is happening so keep that in mind if users are accessing the system. I just schedule mine off hours.
Jim
Hindsight is 20/20
