Service Guard vgexport and lvmtab inconsistent

[stephen corcoran_1]

Here is the output of ioscan, it doesnt show that disk

[LUSMMXP2-root]# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
==========
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 36.4GMAS3367NC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 36.4GMAS3367NC
/dev/dsk/c2t1d0 /dev/dsk/c2t1d0s2 /dev/rdsk/c2t1d0 /dev/rdsk/c2t1d0s2
/dev/dsk/c2t1d0s1 /dev/dsk/c2t1d0s3 /dev/rdsk/c2t1d0s1 /dev/rdsk/c2t1d0s3
disk 6 0/1/1/1.9.0 sdisk CLAIMED DEVICE HP 73.4GST373307LC
/dev/dsk/c3t9d0 /dev/rdsk/c3t9d0


[LUSMMXP2-root]# mount -v
/dev/vg00/lvol3 on / type vxfs ioerror=nodisable,log,dev=40000003 on Thu Jan 19 01:04:38 2006
/dev/vg00/lvol1 on /stand type vxfs ioerror=mwdisable,log,nodatainlog,tranflush,dev=40000001 on Thu Jan 19 01:04:39 2006
/dev/vg00/lvol8 on /var type vxfs ioerror=mwdisable,delaylog,nodatainlog,dev=40000008 on Thu Jan 19 01:04:50 2006
/dev/vg00/lvol7 on /usr type vxfs ioerror=mwdisable,delaylog,nodatainlog,dev=40000007 on Thu Jan 19 01:04:50 2006
/dev/vg00/lvol4 on /tmp type vxfs ioerror=mwdisable,delaylog,nodatainlog,dev=40000004 on Thu Jan 19 01:04:51 2006
/dev/vg00/lvol9 on /spare type vxfs ioerror=mwdisable,largefiles,delaylog,nodatainlog,dev=40000009 on Thu Jan 19 01:04:51 2006
/dev/vg00/lvol6 on /opt type vxfs ioerror=mwdisable,delaylog,nodatainlog,dev=40000006 on Thu Jan 19 01:04:51 2006
/dev/vg00/lvol5 on /home type vxfs ioerror=mwdisable,delaylog,nodatainlog,dev=40000005 on Thu Jan 19 01:04:51 2006
-hosts on /net type autofs ignore,indirect,nosuid,soft,nobrowse,dev=4c000000 on Thu Jan 19 01:05:18 2006
/dev/vg01/lvol1 on /shared type vxfs ioerror=mwdisable,delaylog,nodatainlog,dev=40010001 on Thu Jan 19 01:28:50 2006


Thanks !

[Lolupee]

What is realy your goal here.

If you are looking for the disk, then find it. It either has a hardware failure or the link is down. There is nothing we can do from the forum.


If it has to do with propagating the map file of a single disk, then let me know. It seems we are loosing focus.

[stephen corcoran_1]

Ok

Some background, we lost P1 node because an engineer had deleted system files so we moved the package to the P2 node.

We then reinstalled unix & configured MC/SC on the P1 node

I then exported the shared vg01 from P2 and imported it to P1

At this point I attempted to bring P1 back into the cluster which was successful, using cmrunnode

When I tried to halt the package on P2 and activate it on P1, it failed. At this point I traced back thru my import etc to find out what could be wrong, and this has highlighted the inconcistencies with devices

[stephen corcoran_1]

Perhaps becuase the cluster is actually working even with a missing disk then perhaps we should try and propogate the map file for that single disk and go from there ?

[melvyn burnard]

Sorry, but you seem to be missing the point here.
You have a disk problem, there seems to be one missing. Until you fix that, you are wasting yopur time trying to import/export vgss.

[Lolupee]

Eric,

get something clear. Do you have only one drive and the other device address is just the redundancy or you have 2 drives in that volume group?

If you have only one drive, do you want to use the drive with no HA for this purpose. which means we could forget about the missing drive.

The system you reinstalled, was it an ignite image, restore from backup or from scratch. If not an image, did you delete the node from the working node and then recreate or you just created a new cluster in the new node.