Veritas Volume Manager 5.1 SP1 RP1 (Linux) introduces device detection of ASM devices along with safeguards
Article ID: 100004569
Updated On:
Resolution
Alongside the ASM device detection, VxVM 5.1 SP1 RP1 also introduces device protection for such devices.
VxVM will no longer permit the user to initialize a disk controlled by ASM.
Sample VxVM CLI command output
# vxdisksetup -i emc_clariion0_1041
VxVM vxdisksetup ERROR V-5-2-3523 emc_clariion0_1041: Disk is in use
# vxdisksetup -fi emc_clariion0_1041
VxVM vxdisksetup ERROR V-5-2-5252 emc_clariion0_1041: is already in use by ASM. You can not put this disk under VERITAS Volume Manager control
# vxdisk -f init emc_clariion0_1041
VxVM vxdisk ERROR V-5-1-3421 Device emc_clariion0_1041 is already in use by ASM.
# vxdiskunsetup emc_clariion0_1041
VxVM vxdiskunsetup ERROR V-5-2-3522 emc_clariion0_1041: Disk is not a volume manager disk
Note: If you still want to initialize the disk under VxVM, please remove the ASM signature from the disk using 'dd' command or the other tool.
Applies To
Linux
Issue/Introduction
Sample output
DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR
disk_0 auto:none - - online invalid sdb -
disk_1 auto:none - - online invalid sda -
emc_clariion0_1040 auto:sliced c02141040 stevlx1248_dg01 online thinrclm sdh tprclm VRAID
emc_clariion0_1041 auto:ASM - - ASM sdg tprclm VRAID
Additional Information
