VERITAS Volume Manager 3.5 Installation Guide (August 2002)

Chapter 3, Setting up the VxVM Environment
Initializing VxVM
37
LVM disksareautomatically excludedfromVxVM control and donot needto be addedto
the /etc/vx/disks.exclude file. No Volume Manager utility can be used to initialize
an LVM-controlled disk. You must take specific actions to remove a disk from LVM
control before attempting to place it under VxVM control.
Volume Manager utilities recognize file systems on raw disks (not under LVM control).
Raw disks with file systems cannot be placed under Volume Manager control without
administrator confirmation that the disk file system be destroyed. However, to avoid any
possible confusion, enter these disks in the disks.exclude list.
Raw disks in use by other managing agents, such as databases, are not automatically
recognized by VxVM utilities. These disks are good candidates for inclusion in the
disks.exclude file.
The disks.exclude file is not created by VxVM software installation. To add disk
names to this file, you must create the file. To list a disk in the file, enter only the base
device file name. For example:
c0t0d0
c0t2d0
c1t10d0
To add disks that are in use by LVM volumes to the disks.exclude file, add all disks in
the volume group to which the disk belongs. For example:
# for i in ‘vgdisplay -v uservg | egrep dsk | awk ’{print $3}’‘
> do
> basename $i
> done
Note At least one disk must remain in rootdg at all times while VxVM is running.
Excluding Controllers from VxVM Control
The /etc/vx/cntrls.exclude file is used to exclude controllers. When the name of a
disk controller is added to this file, VxVM does not initialize or control all disks on the
controller.
The following is an example of the file’s contents:
c1
c3
c8