Quorum not present, or some physical volume(s) are missing

[Fabio Della Penna]

Hi to all,
i'm trying to move a LUN on EMC clariion cx500 from hostA to hostB. I executed the following commands:
hostA# vgexport -p -v -m /tmp/vg04.map dev/vg04
hostA# umount /dev/vg04/lvol1
hostA# lvremove /dev/vg04/lvol1
hostA# vgexport /dev/vg04

on hostA then I have unbound the lun, I've removed the dead path pointing to the devices using "powermt check" and I removed by "rmsf" the special files, then I have bound the same lun to the hostB and i moved the map file from hostA to hostB.

hostB# mkdir /dev/vg03
hostB# mknod /dev/vg03/group c 64 0x030000
hostB# vgimport -v -m /tmp/vg04.map /dev/vg03 /dev/dsk/c8t0d3
Beginning the import process on Volume Group "/dev/vg03".
vgimport: Warning: Volume Group belongs to different CPU ID.Can not determine if Volume Group is in use on another system. Continuing.
vgimport: Warning: Volume Group contains "0" PVs, "1" specified. Continuing.
vgimport: Quorum not present, or some physical volume(s) are missing.
Logical Volume is not defined on any physical volume. "/dev/vg03/lvol1" is missing Physical Volumes.
Volume group "/dev/vg03" has been successfully created.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after activating the volume group.

hostB# vgchange -a y /dev/vg03
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c8t0d3":
Cross-device link
vgchange: Warning: couldn't query physical volume "/dev/dsk/c8t0d3": The specified path does not correspond to physical volume attached to this volume group
vgchange: Warning: couldn't query all of the physical volumes.
vgchange: Couldn't activate volume group "/dev/vg03": Quorum not present, or some physical volume(s) are missing

What's wrong?

[Devender Khatana]

Hi,

How many LVOLs this VG consists off? One of them you have allready removed prior ro vgexport on hostA. This will not be available on hostB anyway.

The important fact here would be to try vgimport without map file. As the information in device file is not current. You created map file, them removed one LVOL and then exported the VG. In such scenario do not mention the device file and try vgimport.

The other possibility is that the same disk was accessible through more than one path earlier on host A and was accessible thorugh more than one device name. If this was the case you can try activating VG using

#vgchange -a y -q n /dev/vg03

Followed by this you can find out the devices linked to this VG by doing

#strings /etc/lvmtab

&

#vgdisplay -v /dev/vg03

HTH,
Devender

[Tvs]

hi

from host b can u pls check the disk is detected. by ioscan command.

# ioscan -fnC disk | grep /dev/dsk/c8t0d3

regards

tvs

[Fabio Della Penna]

Hi, thanks for your fast replies.
Every LUN on EMC is reachable from two path, so two special file are linked to it.
During my test i tried also to use "vgimport"
on both of them without success, and so i tried "vgimport" on just one of the two disks but ...
i got the error message you read.
I've used "lvremove" just to have a clean situation oh hostA after moving the LUN to hostB, since i get an error using to erase the volume group from hostA telling me i had a logical volume present on the volume group.
Maybe i was confused, instead of vgexport i was using vgremove??? If "lvremove" has an impact not only on the logical data and special file but get the data unavailable mounting the same lun on another host, i will try to do the same without using "lvremove". My intention is to redact a procedure in case of disaster ricovery, i mean if hostA fails i'd like to mount the LUN on hostB without losing any data. If hostA arises again, i'd like to have a clean situation on it (the volume group does not exist anymore, special files ...).
I will let you know as sonn as i do the new test (using vgexport without executing lvremove before ...)

[Domenico_5]

Hi Fabio

You remember me???

like my hydraulic engineer say: "Here we need someone that understand it".

[Domenico_5]

ok

fabio export the volume with -s option and all work


domviz

[Fabio Della Penna]

Hi to all and thanks,
i'm sorry but in my tests i was sure to be using vgexport but i was using vgremove to remove the volume group on hostA!

FYI: in the further steps, i used the map file to import the volume and i used "vgchange -a y" without any other options to activate it.

PS: Hi Domenico, nice to hear news from you:
I remember you, sure, i hope you are well. Greetings