AIX 5L Problem Determination - IBM Redbooks

ODM corruption can also occur if an LVM operation terminates abnormally and
leaves the ODM in an inconsistent state. This may happen, for example, if the file
system on which the ODM resides (normally root, /) becomes full during the
process of importing a volume group.
If you suspect that the ODM entries for a particular volume group have been
corrupted, a simple way to resynchronize the entries is to varyoff and export the
volume group from the system, then import and varyon to refresh the ODM. This
process can only be performed for non-rootvg volume groups.
For the rootvg volume group, you can use the redefinevg command, which
examines every disk in the system to determine which volume group it belongs to
and then updates the ODM. For example:
# redefinevg rootvg
If you suspect that the LVM information stored on disk has become corrupted,
use the synclvodm command to synchronize and rebuild the LVCB, the device
configuration database, and the VGDAs on the physical volumes. For example:
# synclvodm -v myvg
If you have a volume group where one or more logical volumes is mirrored, use
the syncvg command if you suspect that one or more mirrored copies has
become stale. The command can be used to resynchronize an individual logical
volume, a physical disk, or an entire volume group. For example:
# syncvg -l lv02
The above command synchronizes the mirror copies of the logical volume lv02.
# syncvg -v myvg
The above command synchronizes all of the logical volumes in the volume group
myvg.
7.2.4 Understanding importvg problems
If importing a volume group into a system is not possible using the importvg
command, the following areas are the typical problem areas:
► AIX version level
► Invalid PVID
► Disk change while volume group was exported
► Shared disk environment
In general, if the importvg command is unsuccessful, check the error log for
information that can point to the problem.
Chapter 7. LVM, file system, and disk problem determination 141