vg00 no more in /etc/lvmtab

[Devender Khatana]

Hi,

You just mentioned that it is a cluster configuration. Is it a cluster configuration you are trying to set up? If yes on first node if you have done vgexport without -p option then it will remove information from lvmtab. I doubt that you are not doing this.

Just clarify your situation a bit. Are packages running ?

HTH,
Devender

[Saravanan_15]

Nieu,
You can try to import the vg. Try this one,

# vgimport -v /dev/vg00 /dev/dsk/c0t5d0 /dev/dsk/c0t6d0


good luck...

Regards,
Saravanan M

[Mark Nieuwboer]

The cluster is running fine also the packages.
I didn't do a vgexport of vg00 luckely.
The cluster is a week old.
a read something about
crw-rw---- 1 root root 64 0x000000 May 23 12:52 slvmvg
if this is wrong what to do.

also tried a vgimport of vg00 but what i thought is right you can't vgimport an actief vg.

[Devender Khatana]

Hi,

Oh yes, I think vg00 should be a cluster VG if your system is booting through lvm. It is a misconfigured system. Have you tested package switching etc. before finally handling it over.

It actually require a bit more information to tell everything in detail.

Attach the following :-

$strings /etc/lvmtab
$ioscan -fnC disk
$cmviewcl -v
On which node is your package running. Is it on the same node where problem exists?
How many nodes form this cluster?

HTH,
Devender

[Devender Khatana]

My applogies.
I mean to say vg00 should not be a cluster VG aas system boots from it and therefore other node can not activate it in exclusive mode.

HTH,
Devender

[Mark Nieuwboer]

Hi,

vg00 is not a cluster volumegroup.
for the cluster we have separte vg's.
the problem is not an the second cluster.
All the other vg the systems sees in the lvmtab except vg00.
it's a 2 node cluster with 4 packages equal shared over the cluster.
vg00 Is not a volumegroup of a clusterpackages.

grtz. Mark

[Senthil Kumar .A_1]

output ioscan -fnCdisk

disk 0 0/0/0/3/0.5.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 1 0/0/0/3/0.6.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c0t6d0 /dev/rdsk/c0t6d0

the output from pvdisplay =
pvdisplay -v /dev/dsk/c0t6d0
pvdisplay: Couldn't find the volume group to which
physical volume "/dev/dsk/c0t6d0" belongs.
pvdisplay: Cannot display physical volume "/dev/dsk/c0t6d0".

Hi nieu,

These were your previous responses. The system has two HDD and the second output shows that, the c0t6d0 is not a part of LVM. So lets assume that c0t5d0 is a part of LVM and surely sould be part of VG00.

I need the following details.

1) ll -l /dev/vg*
2) strings /etc/lvmtab ( current lvmtab file ,even if it is corrupt).
3) lssf /dev/rdsk/c0t6d0
4) lssf /dev/rdsk/c0t5d0
5) pvdisplay -v /dev/dsk/c0t5d0

These infos i hope might suffice to check whats the problem...
Will wait for ur response.

[Cem Tugrul]

As an addition to Senthil,

You may also need to check;
#lvlnboot -v

-v Print verbose messages. With no other
arguments present, print information on root,
boot, swap, and dump logical volumes. If a
combined root-boot volume is configured, no
information for the boot volume is displayed.

[Ermin Borovac · Accepted solution]

I think this is a known problem. Are you running 11.00?

If so, check if you have the following patch installed?

Patch Name: PHCO_24437
Patch Description: s700_800 11.00 LVM commands cumulative patch

*** START PATCH NOTES ***
( SR: 8606111918 CR: JAGab84052 )
The vgscan command puts a bogus entry in the lvmtab
file, when a special file /dev/slvmvg is present
with the same minor number as /dev/vg00.

( SR: 8606111918 CR: JAGab84052 )
vgscan looks for all special files with major number
0x64 under /dev and assumes that the directory in which
it is present is a volume group name.

Resolution:
The vgscan command is modified to check the group file
under each volume group directory.
*** END PATCH NOTES ***

/etc/slvmvg is created by SG. You can move it away to /tmp (stop the cluster) and re-run vgscan. slvmvg should be re-created when you restart cluster with cmruncl.

[Saravanan_15]

Hi Nieu,
From the error messages reported by vgscan command,
"vgscan: has no correspoding valid raw device file under /dev/rdsk.
Verification of unique LVM disk id on each disk in the volume group
/dev/vg00 failed."

it seems to be problem with raw disk device files. and also see the timestamp of your raw device files,

crw-r----- 1 bin sys 188 0x005000 May 9 07:44 c0t5d0
crw-r----- 1 bin sys 188 0x006000 May 9 07:44 c0t6d0

It's showing may 9. Any modification you did.try to remove the raw device files using 'rmsf' command, and re-install the special files using "insf -e". Now move the lvmtab file, and run "vgscan -av".

Regards,
Saravanan M