Veritas Storage Foundation 5.1 SP1 Advanced Features Administrator"s Guide (5900-1503, April 2011)

MWC volume being full, leaving no space for the DRL log. However it is very
unlikely that this situation would occur. Note that the MWC and DRL are used
only when the system crashes or is improperly shut down, to quickly bring all
mirrors in the volume back into a consistent state.
■ A volume group containing the /usr file system.
For this release, a volume group containing the /usr file system cannot be
converted because vxvmconvert needs access to files in /usr.
■ Volume groups with any dump or primary swap volumes.
Because this release does not support rootability, vxvmconvert will not convert
any volume group with dump or primary swap volumes. These are volumes
known to the boot process. However, swap volumes on volumes other than the
root volume can be converted (as long as this volume is not in the same volume
group as the root volume).
■ Volume group disks used in MC/ServiceGuard clusters.
The conversion process does not support conversion of any volume group that
is marked as a member of a MC/ServiceGuard or OPS Edition high availability
cluster. The volume group must be deactivated and removed from membership
in the high availability cluster before it can be converted.
■ Volume groups and logical volumes with large number of characters in the
name.
If you convert an LVM volume group with more than 31 characters in the
volume group name, VxVM will retain only the first 31 characters of the LVM
volume group name. Conversion of a logical volume containing more than 28
characters in the logical volume name is not supported.
See “List of conversion error messages” on page 507.
■ Volume groups or logical volumes containing special characters
Conversion of volume groups or logical volumes containing special characters
like #, $, *, _ in the name, is not supported.
■ Volume groups used for cluster lock disks.
The conversion process does not support conversion of a volume group that
contains a disk that is being used for a cluster lock disk for an MC/ServiceGuard
cluster.
■ Volume groups with any disks that have bad blocks in the bad block directory.
Unlike LVM, VxVM does not support bad block revectoring at the physical
volume level. If there appear to be any valid bad blocks in the bad block
directory of any disk used in an LVM volume group, the group cannot be
converted.
See “List of conversion error messages” on page 507.
Offline data migration
Converting LVM to VxVM
404