vgimport continued from last query

[khilari]

The state on server1:

# ioscan -fnC disk

Class I H/W Path Driver S/W State H/W Type Description

==========================================================================

disk 0 1/0/0/3/0.6.0 sdisk CLAIMED DEVICE HP 36.4GMAU3036NC

/dev/dsk/c0t6d0 /dev/rdsk/c0t6d0

disk 1 1/0/0/3/1.2.0 sdisk CLAIMED DEVICE _NEC DVD_RW ND-

3540A

/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0

disk 2 1/0/1/1/0/1/1.6.0 sdisk CLAIMED DEVICE HP 36.4G

MAU3036NC

/dev/dsk/c3t6d0 /dev/rdsk/c3t6d0

disk 3 1/0/6/1/0.8.0.110.0.0.0 sdisk CLAIMED DEVICE HP

A6189B

/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0

disk 4 1/0/6/1/0.8.0.110.0.0.1 sdisk CLAIMED DEVICE HP

A6189B

/dev/dsk/c6t0d1 /dev/rdsk/c6t0d1

# diskinfo /dev/dsk/c3t6d0

diskinfo: Character device required

# diskinfo /dev/rdsk/c3t6d0

SCSI describe of /dev/rdsk/c3t6d0:

vendor: HP 36.4G

product id: MAU3036NC

type: direct access

size: 35566480 Kbytes

bytes per sector: 512



The shared volume is c3t6d0 (that’s what I think ).



# strings /etc/lvmtab

/dev/vg00

/dev/dsk/c0t6d0

/dev/vg01

/dev/dsk/c6t0d1

/dev/vg03

/dev/dsk/c3t6d0 showing the volume group has c3t6d0 in it, then y vgimport is saying that it Couldn't access the list of physical volumes for volume group "/dev/vg03".





--- Logical volumes ---

LV Name /dev/vg03/mcsg

LV Status available/syncd

LV Size (Mbytes) 300

Current LE 75

Allocated PE 75

Used PV 1





--- Physical volumes ---

PV Name /dev/dsk/c3t6d0

PV Status available

Total PE 8681

Free PE 8606

Autoswitch On



# mount -v

/dev/vg00/lvol3 on / type vxfs log on Wed Mar 22 11:18:43 2006

/dev/vg00/lvol1 on /stand type hfs defaults on Wed Mar 22 11:18:43 2006

/dev/vg00/lvol8 on /var type vxfs delaylog,nodatainlog on Wed Mar 22 11:18:45 20

06

/dev/vg00/lvol7 on /usr type vxfs delaylog,nodatainlog on Wed Mar 22 11:18:46 20

06

/dev/vg00/lvol4 on /tmp type vxfs delaylog,nodatainlog on Wed Mar 22 11:18:46 20

06

/dev/vg00/lvol6 on /opt type vxfs delaylog,nodatainlog on Wed Mar 22 11:18:46 20

06

/dev/vg00/lvol5 on /home type vxfs delaylog,nodatainlog on Wed Mar 22 11:18:46 2

006

/dev/vg03/mcsg on /mcsg type vxfs log,nodatainlog on Mon Mar 27 11:36:32 2006



# vgexport -psv -m /tmp/mcsg.map /dev/vg03

Beginning the export process on Volume Group "/dev/vg03".

vgexport: Volume group "/dev/vg03" is still active.

/dev/dsk/c3t6d0



# rcp /tmp/mcsg.map newFIN:/tmp/mcsg.map



# cat /tmp/mcsg.map

VGID 920bc9324422efd5

1 mcsg







































Server2:



# ioscan -fnC disk

Class I H/W Path Driver S/W State H/W Type Description

==========================================================================

disk 0 1/0/0/3/0.6.0 sdisk CLAIMED DEVICE HP 36.4GMAU3036NC

/dev/dsk/c0t6d0 /dev/rdsk/c0t6d0

disk 1 1/0/0/3/1.2.0 sdisk CLAIMED DEVICE _NEC DVD_RW ND-

3540A

/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0

disk 2 1/0/1/1/0/1/1.6.0 sdisk CLAIMED DEVICE HP 36.4G

MAU3036NC

/dev/dsk/c3t6d0 /dev/rdsk/c3t6d0

disk 3 1/0/6/1/0.8.0.108.0.0.0 sdisk CLAIMED DEVICE HP

A6189B

/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0

disk 4 1/0/6/1/0.8.0.108.0.0.1 sdisk CLAIMED DEVICE HP

A6189B

/dev/dsk/c6t0d1 /dev/rdsk/c6t0d1

# diskinfo /dev/dsk/c3t6d0

diskinfo: Character device required

# diskinfo /dev/rdsk/c3t6d0

SCSI describe of /dev/rdsk/c3t6d0:

vendor: HP 36.4G

product id: MAU3036NC

type: direct access

size: 35566480 Kbytes

bytes per sector: 512





# cat /tmp/mcsg.map

VGID 920bc9324422efd5

1 mcsg





# vgimport -spv -m /tmp/mcsg.map /dev/vg03

Beginning the import process on Volume Group "/dev/vg03".

Couldn't access the list of physical volumes for volume group "/dev/vg03".

[Prashant Zanwar_4]

Did you try a pvdisplay on your devices, chance is that it is a alternate link to other device..?

Thanks and regards
Prashant

[khilari]

well, on the 1st server it is showing all the free extents and on server 2 it is showing # pvdisplay -v /dev/dsk/c3t6d0
pvdisplay: Couldn't find the volume group to which
physical volume "/dev/dsk/c3t6d0" belongs.
pvdisplay: Cannot display physical volume "/dev/dsk/c3t6d0".

Any suggestions??

[Siddhartha M]

did you create the volume group device directory and the group special file on server 2 for vg03 before executing vgimport?


mkdir /dev/vg03
mknod /dev/vg03/group c

-Siddhartha

[Muthukumar_5]

Before vgimport step,

# vgscan -v

# mkdir /dev/vg03
# mknod /dev/vg03/group c 64


Then vgimport step.

Refer this:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=497609

--
Muthu

[Patrice Le Guyader]

Hello Hilari,

It seem that you're working on VA7100
Can you post the result of the following commands :

armdsp -i or armdiscover

How many of these array have you ? two ? :-]

Regards
Pat

[YoungHwan, Ko]

At Server2, make device file for vg03
# mkdir /dev/vg03
# mknod /dev/vg03/group c 64 0x030000

and then import volume group
# vgimport -v -s -m /tmp/mcsg.map /dev/vg03

Regards..

[Prashant Zanwar_4]

what do vgdisplay on VG shows which is present on one host? is it in read/write exclusive or ?
what does pvdisplay on the device in question shows where VG is present?
Are the paths same on both hosts for the devices you are trying to import the VG with?
If no what should be path on other host?
If yes, did you check if there is VG already present on other host?
Or strings lvmtab and check what are entried it is showing?
You have to do tricks around to work it out..

Regards
Prashant

[Kent Ostby]

Was the device presented to both servers from the array?

[Victor Makukha]

Hi Khilari,

I've got almost the same situation (I have EVA 4000 connected to two nodes: RP8420 and RP7420). The device names for the EVA LUNs are different on these two nodes (I have 1 main and 7 alternative PV links to each LUN). After I had exported a VG from one node to another with a -s -m options and tried to import in on another one with reading this map file I received the same error. The situation is the same even if I use the modified device list file. It seems that it just ignores it. Do you have any update on this problem? Do you have cluster software installed? Which version do you use?

[Arunkumar.B]

HI Khilari,

The disk is getting detected on both disk.You have exported the vg with correction options also...But while importing u are mentioning as

vgimport -spv -m /tmp/mcsg.map /dev/vg03

Actually u should do like this:

mkdir /dev/vgname
mknod /dev/vgname/group c 64 01x0000
vgimport -v -s -m /tmp/mcsg.map /dev/vg03

Don't use -p for importing it will not allow to update the lvmtab

Pls try this...

[Ninad_1]

Hi Khilari,

The -s option causes vgimport to scan the system for disks with the same vg_id as mentioned in the map file and since it is reporting that its not able to access the physical volumes, it surely must be not able to see the disks.
I very much suspect that
a. Either the shared disk is not visible to server2 (You are probably assuming that the disk name should be same on both the servers, but in reality it can be different as well)
OR
b. The device file is corrupted or something

For
a. Check that the disk is made visible to the 2nd server.
For
b. Try deleting the device file entires for c3t6d0 by rmsf (assuming that this device is not being used by any other VG) and then recreate the device files using insf -e

Regards,
Ninad

[Victor Makukha]

Hi Ninad,

Is it OK if I take Khilari's side, she will give her answers in any case. :))). As for me I've checked that my EVA is accessible for sure. I tried to reinstall the device files. Did not help. I removed VG from the 1st node (freed up one EVA LUN from the 1st node) then created the same VG on that EVA LUN from the second node - successfull! But it doesn't work for export-import!

[Ninad_1]

Victor,

I would advice you to start your own thread rather than adding to this thread as it may lead to a totally different route which may not be of any use to the owner of this thread.
Simply start a thread and the whole forum is there for your help.

Regards,
Ninad