Veritas Volume Manager 5.0.1 Migration Guide, HP-UX 11i v3, First Edition, November 2009

Table 3-3
Additional VxVM tasks with no LVM equivalents (continued)
ExamplesTask descriptions
vxassist remove log vol_nameRemove a log from a volume.
vxsd mv old_subdisk new_subdiskMove a subdisk.
vxsd join subdisk1 subdisk2 new_subdiskJoin subdisks.
Existing features in LVM not supported in VxVM
Some of the existing features in LVM are not supported in the current release of
VxVM. Given below is a table with the unsupported LVM features, and possible
workarounds in VxVM.
Table 3-4
LVM features and VxVM equivalents
VxVM EquivalentLVM Feature
VxVM has no equivalent feature. The disk group feature
of VxVM combines the logical volume group (VG) and
physical volume group (PVG) of LVM.
Physical volume groups
Powerfail timeout feature: After the EPOWERF error
condition disappears, the reconfiguration command must
be run manually to re-enable the paths and the disks
which were disabled due to EPOWERF error. Additional
information is available.
See the pfto feature in the vxdctl(1M) manual page.
Powerfail timeout feature: Automatically re-enable a disk
or a path to a disk, after temporary error condition
(resulting inEPOWERF error on I/Os) disappears on that
disk or path.
VxVM does not support the LVTO feature. However,
VxVM supports the powerfail timeout feature to handle
transient error conditions. By default, the use of PFTO is
disabled in the HP-UX native multipathing devices. In
case of DMP devices the use of PFTO is enabled. However,
you can change the PFTO settings.
See the powerfail timeout feature and the pfto feature
in the vxpfto manual pages.
Logical Volume Timeout (LVTO). If LVTO on a logical
volume is set to zero, which is the default, an I/O is retried
forever.
VxVM relocates whole subdisks. Smaller granularity
relocation is not supported. The bad block reallocation
feature does not exist in VxVM because the vectoring of
bad blocks is now done by most hardware.
Bad media block relocation.
71Command differences
Existing features in LVM not supported in VxVM