Note: Converting 1k blocks to 512 byte blocks 2097152 * 2 = 4194304
After a failed resize:
The best path to correct the volume/file system size difference is to correct the issue that is preventing fsadm from executing during a vxresize operation and re-run the original command.
Alternatively, you can safely resize the volume back to its original size if the exact original block size is known. This is done using the vxassist shrinkto command. Please note that by default this command will produce an error message.
Use the '-f' option if you can confirm the previous volume size.
Question:
Can a volume be shrunk safely when it is larger than the file system on the volume?
This condition can occur as a result of an error with the fsadm command during a vxresize operation (either initiated on the command line or through the GUI). Error conditions during a resize will ordinarily revert the volume to its original size but in some circumstances the volume may remain at the target size, while the file system is still the original size.
Example:
Original volume 'tvol' is 2 gigabytes (4194304 blocks) with a file system. Note the file system is slightly smaller due to fs meta data.