Veritas Volume Manager co-existence with Oracle Automatic Storage Management (ASM) disks

ASM disks are the disks used by Oracle Automatic Storage Management software. Veritas Volume Manager (VxVM) co-exists with Oracle ASM disks, by recognizing the disks as the type Oracle ASM. VxVM protects ASM disks from any operations that may overwrite the disk. VxVM classifies and displays the ASM disks as ASM format disks. You cannot initialize an ASM disk, or perform any VxVM operations that may overwrite the disk.

If the disk is claimed as an ASM disk, disk initialization commands fail with an appropriate failure message. The vxdisk init command and the vxdisksetup command fail, even if the force option is specified. The vxprivutil command also fails for disks under ASM control, to prevent any on-disk modification of the ASM device.

Disks that ASM accessed previously but that no longer belong to an ASM disk group are called FORMER ASM disks. If you remove an ASM disk from ASM control, VxVM labels the disk as a FORMER ASM disk. VxVM enforces the same restrictions for FORMER ASM disks as for ASM disks, to enable ASM to reuse the disk in the future. To use a FORMER ASM disk with VxVM, you must clean the disk of ASM information after you remove the disk from ASM control. If a disk initialization command is issued on a FORMER ASM disk, the command fails. A message indicates that the disk must be cleaned up before the disk can be initialized for use with VxVM.

To remove a FORMER ASM disk from ASM control for use with VxVM

  1. Clean the disk with the dd command to remove all ASM identification information on it. For example:
    dd if=/dev/zero of=/dev/rdsk/<wholedisk|partition> count=1 bs=1024

    Where wholedisk is a disk name in the format: cxtydz

    Where partition is a partition name in the format:cxtydzsn

  2. Perform a disk scan:
    # vxdisk scandisks

To view the ASM disks

To check if a particular disk is under ASM control