Example:

1) The volume/file system is busy at the time of the vxresize command and the blocks are currently in use.

Solution: Try again later at off-peak hours.


2) The file system is fragmented.

Solution: Run Fragmentation report and defragment.

# /opt/VRTS/bin/fsadm -ED

# /opt/VRTS/bin/fsadm -de -s -t 1800 /      

The -s option prints a summary at the end of each pass. This will defragment the file system  for 1800 seconds and then stop. (See fsadm man page.)  Run the command repeatedly if fragmentation is still reported. A heavily fragmented file system can cause fsadm to fail with error 28, which typically means a 100% full file system, but in this case, it is not.  

Determining Fragmentation

To determine whether a file system is fragmented, the free extents of that file system must be examined. If a large number of small extents are free, there is fragmentation.If more than half of the amount of free space is used by smaller extents (smaller than 64 blocks), or there is less than 5 percent of total file system space available in large extents, there is serious fragmentation.

Running The Extent-fragmentation Report

The extent-fragmentation report provides detailed information about the degree of fragmentation in a given file system. The command syntax for an extent-fragmentation report is:

# fsadm -E[-l largesize] [-r rawdev] mount_point