Hi,
Theoritically, there are two different scenarios which might be possible in the problem you are describing as "metadata corruption"
1. Filesystem metadata corruption: In this case, the volume beneath is fine & is in "Enabled Active" state however the there were some IO errors (hard or soft) or there was some problem writing to data region, there are some possibilities where filesystem may get corrupted. In this case, you will need to execute fsck the filesystem with right options to fix the problem. The problem may fix or may not depending on extent of filesystem corruption.
2. VxVM private region corruption: vxvm disks have 2 regions i.e private region & public region. If in case diskgroup is lost or destroyed or corrupted, you may not be able to see the diskgroups or volumes in it. Another possibility is someone accidently deleted a volume. In such situations you will need to create the diskgroup or volumes manually. There are multiple outputs that can help here, for e.g if you have configuration backup in /etc/vx/cbr/bk or if you have veritas explorer or if you have a "vxprint -mvphsr" output , you can easily rebuild the diskgroup & the volumes.
The steps what I have explained in my previous comment like initializing the disk again with right values like puboffset, privoffset, privslice, pubslice or recreating the volume using vxmake command can fix above scenarios where volume was lost for some reason.
Now, if in case someone has touched public region, for e.g lets take for a scenario that storage lun beneath the volume was accidently decommissioned & assigned to other server & other server did write on the Lun. There are high chances that public region has been damaged which removes the chances of restoring the data by reassigning the Lun or recreating the volume once Lun is assigned back. In such cases, restoring from backup would be the choice.
Simple point to remember is, vxmake, recreating the volume can only help if underneath storage Lun or disk is untouched or intact & presumably superblock of filesystem on the public region is intact as well, there are high chances you can get the data.
G