Cannot Add alternate PV to a VG

[Tuck Lee]

I am doing a vgextend for alt links

[Raj Briden]

alternate method.

export the VG and import with alternate link details.

check man page for

#vgchange
#vgexport
#vgimport

[SoorajCleris]

Take lvmtab backup

do a vgscan

Regards,
Sooraj

[Kapil Jha]

First thing you have power path installed so you should not worry about anything cause power path handles the multi path.

your lvmtab has
vg00 >>> diskXX
vg01 >>> cXdXtX

I think you should change it to dsf name
by

/usr/contrib/bin/vgdsf â c

Read the below document carefully.

http://docs.hp.com/en/LVMmigration1/LVM_Migration_to_Agile.pdf

Do you have lvmtab_p??

BR,
Kapil+

[RC Park]

Hi Tuck! I don't know, maybe I missed something here, but maybe not... Looks like you accidentally crossed the two naming conventions, and that is all that is going on; I'm guessing if you try again with the correct device name you'll have more success:

You have above:
I tried using the /dev/dsk/disk66 got this error;
vgcreate -s 8 -p 32 vg02 /dev/dsk/disk66
vgcreate: Physical volume "/dev/dsk/disk66" is not a block special file

TRY THIS:
vgcreate -s 8 -p 32 vg02 /dev/disk/disk66

and you'll likely have more success.

There's several HP documents on the subject, but I've attached one that should help explain this all perfectly. Here's a simple note from that document:

Typical legacy and persistent DSFs for a LUN are shown below:
Legacy DSF: /dev/dsk/c8t1d3 and /dev/rdsk/c8t1d3 Persistent DSF: /dev/disk/disk66 and /dev/rdisk/disk66

Let us know if this helps, and don't forget to assign points :)

RCP

[Tuck Lee]

I have use the DSF naming to create the Vg again;

root@ [/dev]
# mknod /dev/vg01/group c 64 0x010000

root@ [/dev]
# pvcreate -f /dev/rdisk/disk65
Physical volume "/dev/rdisk/disk65" has been successfully created.

root@ [/dev]
# vgcreate -s 8 -p 32 /dev/vg01 /dev/disk/disk65
Increased the number of physical extents per physical volume to 3236.
Volume group "/dev/vg01" has been successfully created.
Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf

root@ [/dev]
# vgdisplay -v /dev/vg01
--- Volume groups ---
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 0
Open LV 0
Max PV 32
Cur PV 1
Act PV 1
Max PE per PV 3236
VGDA 2
PE Size (Mbytes) 8
Total PE 3236
Alloc PE 0
Free PE 3236
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 809g
VG Max Extents 103552


--- Physical volumes ---
PV Name /dev/disk/disk65
PV Status available
Total PE 3236
Free PE 3236
Autoswitch On
Proactive Polling On



root@ [/dev]
# vgextend /dev/vg01 /dev/disk/disk95
Verification of unique LVM disk id on each disk in the volume group
/dev/vg01 failed.
Following are the sets of disks having identical LVM disk id
/dev/disk/disk65 /dev/disk/disk95

[Kapil Jha]

hmmmm can you please check from cstm or powermt if disk65 and disk95 are same disk or different disk.

Is it your DR server, does it have R2 devices present on the server.

I had the smthing similar issue and I could see the R2 devices on DR servers and hence the error.

RIght now you should confirm R2 device and one more thing, disk65 and disk95 cannot/should not be same disk.

BR,
Kapil+

[Tuck Lee]

disk65 and disk95 are the same LUN just from a different link path

/dev/rdisk/disk65 M(3) EMC SYMMETRIX 5670 15005C5000 26516160
/dev/rdisk/disk95 M(3) EMC SYMMETRIX 5670 15005C5000 26516160
/dev/rdsk/c13t0d3 M(3) EMC SYMMETRIX 5670 15005C5000 26516160
/dev/rdsk/c19t0d3 M(3) EMC SYMMETRIX 5670 15005C5000 26516160

[Kapil Jha]

smthing is wrong....there is no point having 2 dsf device for the same machine.

I would suggest to remove device file for disk65/95 and recreate them again.

BR,
Kapil+

[Kapil Jha]

>>>smthing is wrong....there is no point having 2 dsf device for the same machine.

It should be

smthing is wrong....there is no point having 2 dsf device for the same device.

BR,
Kapil+