VERITAS Volume Manager Storage Administrator (VMSA) and Enterprise Administrator (VEA) allow a disk to be placed under Volume Manager control even if the disk is excluded by /etc/vx/disks.exclude, /etc/vx/cntrls.exclude files or /etc/vx/enclr.exclude.

Article:TECH9420  |  Created: 2004-01-21  |  Updated: 2004-01-21  |  Article URL http://www.symantec.com/docs/TECH9420
Article Type
Technical Solution


Environment

Issue



VERITAS Volume Manager Storage Administrator (VMSA) and Enterprise Administrator (VEA) allow a disk to be placed under Volume Manager control even if the disk is excluded by /etc/vx/disks.exclude, /etc/vx/cntrls.exclude files or /etc/vx/enclr.exclude.

Solution



/etc/vx/disks.exclude, /etc/vx/cntrls.exclude and /etc/vx/enclr.exclude files can be used to exclude disks or controllers or enclosures from VERITAS Volume Manager (VxVM) control.  Refer to the VxVM Administrator's Guide for more information about these files.

VMSA and VEA do not use these files.

Only the vxinstall and vxdiskadm commands use the contents of the /etc/vx/disks.exclude, /etc/vx/cntrls.exclude and /etc/vx/enclr.exclude files.

If the goal is to remove the disk from VxVM view so that user can never mistakenly initialize a disk, then the solution is to suppress or prevent the disk from the VxVM view.  This feature is available via the vxdiskadm command in VxVM 3.1.1 and above.   Refer to the VxVM 3.1.1 (or above) Administrator's Guide and the chapter about Administering Dynamic Multipathing (DMP).  This information is also available in TechNote 237912 (link below under Related Documents).


Supplemental Materials

SourceiTools
Value55821
Descriptionvmsa 3.1 will let you add a disk under vm control even though it is in the disks.exclude file


Legacy ID



233755


Article URL http://www.symantec.com/docs/TECH9420


Terms of use for this information are found in Legal Notices