LVM Migration from Legacy to Agile Naming Model
to migrate a volume group configured with legacy DSFs to use corresponding persistent
DSFs.
Disabling Legacy Naming Model
The rmsf –L command disables the legacy naming model by removing all legacy DSFs and related configuration
information. For additional information on disabling legacy naming model in HP-UX 11i v3, see the
For More
Information section for the white paper HP-UX 11i v3 Persistent DSF Migration Guide. All LVM volume groups
must be migrated to the agile naming model before disabling the legacy naming model. If any active volume
group is still configured with legacy DSFs, the rmsf –L command fails with a message similar to the following:
WARNINGS
Affected Volumes
Volume manager configuration on an affected device
/dev/vg_name
(Unused volume. All paths to one or more PVs configured under this
volume are affected )
PVs under this volume are: /dev/dsk/c0t2d0
Note: The rmsf –L command succeeds if volume groups configured with legacy DSFs are not activated. HP
strongly recommends activating all the LVM volume groups before attempting to disable the legacy naming model.
Impact on LVM commands after the Disablement of Legacy Naming Model
When the legacy naming model is disabled, vgscan and vgimport commands without a –N option, fail with the
following message:
The legacy naming model has been disabled on the system.
Try with the -N option.
The vgscan command when invoked with -a or –B option, fails with the following message:
The legacy naming model has been disabled on the system.
The option being used needs the legacy naming model enabled.
If the legacy naming model is disabled, when there exists inactive volume groups configured with legacy DSFs,
(/etc/lvmtab file has legacy DSFs) any subsequent invocation of pvcreate, vgimport, vgcreate, pvremove, and
vgchgid fails with the following message, irrespective of the physical volume/volume group on which the
command is invoked:
"The legacy naming model is disabled, but the /etc/lvmtab
file still contains legacy devices such as “/dev/dsk/c1t2d3". Command will not succeed
until either the legacy device is removed from the /etc/lvmtab file or the
legacy mode is enabled using insf(1M) -L."
Impact of Native Multi-Pathing on LVM
The mass storage stack in HP-UX 11i v3 provides native multi-pathing functionality, distributing I/O requests
transparently across all available lunpaths to the LUN. For additional information on native multi-pathing for mass
storage, see the
For More Information section for the white paper HP-UX 11i v3 Native Multi-Pathing for Mass
4