< Previous  | TOC | Index | Next  >

Disks under VxVM control

When you add a disk to a system that is running VxVM, you need to put the disk under VxVM control so that VxVM can control the space allocation on the disk. Unless you specify a disk group, VxVM places new disks in a default disk group according to the rules for determining the default disk group.

See "Rules for determining the default disk group" on page 177.

The method by which you place a disk under VxVM control depends on the following circumstances:

• If the disk is new, it must be initialized and placed under VxVM control. You can use the menu-based vxdiskadm utility to do this.
  Warning: Initialization destroys existing data on disks.
  
• If the disk is not needed immediately, it can be initialized (but not added to a disk group) and reserved for future use. To do this, enter none when asked to name a disk group. Do not confuse this type of "spare disk" with a hot-relocation spare disk.
• If the disk was previously initialized for future use by VxVM, it can be reinitialized and placed under VxVM control.
• If the disk was previously in use, but not under VxVM control, you may wish to preserve existing data on the disk while still letting VxVM take control of the disk. This can be accomplished using encapsulation.

  Encapsulation preserves existing data on disks.

• 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 item 17 (Prevent multipathing/Suppress devices from VxVM's view) from the vxdiskadm main menu.

See "Disabling multipathing and making devices invisible to VxVM" on page 144.