Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

For example, use the following commands to destroy the file system and
initialize the disk:
# dd if=/dev/zero of=/dev/dsk/diskname bs=1024k count=50
# vxdisk scandisks
# vxdisk -f init diskname
■ If the disk was previously in use by the LVM subsystem, you can preserve
existing data while still letting VxVM take control of the disk. This is
accomplished using conversion. With conversion, the virtual layout of the
data is fully converted to VxVM control.
Note: This release only supports the conversion of LVM version 1 volume
groups to VxVM. It does not support the conversion of LVM version 2 volume
groups.
See the Veritas Storage Foundation Advanced Features Administrator's Guide.
■ If the disk was previously in use by the LVM subsystem, but you do not want
to preserve the data on it, use the LVM command, pvremove, before attempting
to initialize the disk for VxVM.
■ Multiple disks on one or more controllers can be placed under VxVM control
simultaneously. Depending on the circumstances, all of the disks may not be
processed the same way.
It is possible to configure the vxdiskadm utility not to list certain disks or
controllers as being available. For example, this may be useful in a SAN
environment where disk enclosures are visible to a number of separate systems.
To exclude a device from the view of VxVM, select Prevent
multipathing/Suppress devices from VxVM’s view from the vxdiskadm main
menu.
See “Disabling multi-pathing and making devices invisible to VxVM” on page 152.
Changing the disk-naming scheme
You can either use enclosure-based naming for disks or the operating system’s
naming scheme. VxVM commands display device names according to the current
naming scheme.
The default naming scheme is enclosure-based naming (EBN). When you use DMP
with native volumes, the disk naming scheme must be EBN, the use_avid attribute
must be on, and the persistence attribute must be set to yes.
99Administering disks
Changing the disk-naming scheme