AIX's lspv shows newly assigned LUN as "VeritasVolumes" instead of "None"

book

Article ID: 100001012

calendar_today

Updated On:

Resolution

Depending upon the history of a lun, when assigned to an AIX system, the AIX command lspv may report the lun as "VeritasVolumes"
e.g.
hdisk102        none                                VeritasVolumes
 
AIX's VolumeManager (LVM) deems the disk to be initialised under Volume Manager (VxVM) from Veritas. Therefore, if wanting to use the device for LVM, the device will need to be uninitialised from VxVM, but only once it has been established that the device is no longer needed by VxVM, and is one that can be spared for LVM.
First, ensure that the device can be seen by VxVM by running:
 
# vxdctl enable
 
and, using the output from "vxdisk -e list" to determine the device:
 
# vxdisk -elist|grep hdisk102
ams_wms0_0188auto      -            -            online      hdisk102     std
 
then uninitialise the device to remove the VxVM information:
#/etc/vx/bin/vxdiskunsetup -C ams_wms0_0188
 
Before the device can be reused within AIX's LVM environment, it will also have to be removed from VxVM's view:
# vxdisk rmams_wms0_0188
 
as seen below, lspv now reports the device without the VeritasVolumes tag:
# lspv|grephdisk102
hdisk102        none                                None
 
and an AIX LVMvolume group can now be created:
# mkvg -y lvmvg hdisk102
0516-1254 mkvg:Changing the PVID in the ODM.
lvmvg
 

 

Issue/Introduction

AIX's lspv shows newly assigned LUN as "VeritasVolumes" instead of "None"
Powered by Wolken Software