New disk to be added to VG

[sudhapage]

HI all,

We added the new LUN and that LUN is having the new two disks.

When I am doing vgextend, I got the below error:

godavari# vgextend /dev/vg02 /dev/dsk/c16t0d5 /dev/dsk/c18t0d5
vgextend: Couldn't install the physical volume "/dev/dsk/c16t0d5".
The path does not specify a valid physical volume.
vgextend: Couldn't install the physical volume "/dev/dsk/c18t0d5".
The path does not specify a valid physical volume.
godavari#

Then I have tried pvcreate, that is also showing the below error, can you advise, what need to be done for adding the disks to vg02.

godavari# pvcreate /dev/rdsk/c16t0d5
pvcreate: The physical volume already belongs to a volume group

godavari# pvcreate /dev/rdsk/c18t0d5
pvcreate: The physical volume already belongs to a volume group

godavari# swlist | grep -i online
B3929CA B.11.11.03.03 HP OnLineJFS
OnlineDiag B.11.11.19.01 HPUX 11.11 Support Tools Bundle, June 2007

[TIMOTHY J. REGAN II]

Hello,

Assuming there is a SAN in the picture here.....

The error message you recieved from the pvcreate should only happen if the new LUNS you have recently added to your host belong to another defined Volume Group that is either local or on another server. It may also be possible that these LUNS could have at some point belonged to VG on a your server or a different node no longer associated with the drive and they were never scrubbed of there data; hence the VG header information is still contained on the drives and pvcreate saves your life by not allowing you to proceed.

If these LUNS are SAN based please make sure to verify the electonic serial numbers on the drives are not zoned to more than one host. I cannot stress how dangerous from a data loss perspective this could be if you do not verify the use of these LUNS.

If you have verified no host local or remote have current/defined VGs with these LUNS present then use the -f option with your pvcreate and then vgextend them into your VG.

If these LUNS are simple disk drives added to your host localy ie hot plug or some other JBOD attached container still verify the local use of these devices in other local VGs within your host and if they are not in use you should be ok to proceeed with the same -f option with your pvcreate and then vgextend them into your VG.

Please validate all of your information and GOOD LUCK!!!

Tim

[psreedhar]

use the following command to see if it already has any LVM metadata

# pvdisplay -l /dev/dsk/c18t0d6
/dev/dsk/c18t0d6:LVM_Disk=yes

If it already has metadata then it is your choice about what to do :)

[radkol]

Hi,

The error could be because of tis LUN was used before in HPUX lvm.
check with:
strings /etc/lvmtab
pvdisplay -v
if this lun is part of the current VGs.
you could also check on lower level with adb and xd.
then
pvcreate -f
vgextend

[josinjosek]

try with

pvcreate -f then
vgextend

[Asif Sharif]

#pvcreate -f /dev/rdsk/c16t0d5
#pvcreate -f /dev/rdsk/c18t0d5

#vgextend /dev/vg02 /dev/dsk/c16t0d5 /dev/dsk/c18t0d5

http://www11.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=emr_na-c01027999-1

Regards,
Asif Sharif

[Sajjad Sahir]

once u added a disk from eva
u should give insf -e disk
check ioscan -funC disk
do pvcreate
then add it in u volume group

[AVV]

Hi,

Use -f option along with pvcreate but ensure, that PV is not being used by any VG which does have critical data.

Then you do vgextend , I hope ,it work for you.

Thanks -ajeshvv

[Sajjad Sahir]

u have to assign points to the peoples who answering u questions.