Oop! More volume group problems ...

[Melissa Murphy]

Thanks a bunch guys, but I'm still not completely on my way. I would start over completely, but I can't seem to clean up enough so that I can. I was planning on keeping vg100 where it is on Data and vg67 on Lore the way they're supposed to be. I was going to remove vg67 on Data and vg100 on Lore, which would be mounted in the case of an emergency. So on Data right now I just have vg100, but I still have both of them on Lore. I guess this is what I'm trying to do:

# vgremove /dev/vg100
vgremove: Volume group "/dev/vg100" does not exist in the "/etc/lvmtab" file.
vgremove: Couldn't remove volume group "/dev/vg100".
# mv /etc/lvmtab /etc/lvmtab.old
# vgscan -v
Creating "/etc/lvmtab".
vgscan: Couldn't access the list of physical volumes for volume group "/dev/vg00".
vgscan: Couldn't access the list of physical volumes for volume group "/dev/vg67".
vgscan: Couldn't access the list of physical volumes for volume group "/dev/vg100".
Couldn't stat physical volume "/dev/dsk/c4t0d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c4t0d1":
Invalid argument
Physical Volume "/dev/dsk/c4t0d7" is not part of a Volume Group
Couldn't stat physical volume "/dev/dsk/c2t2d0":
Invalid argument

Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c0t5d0




/dev/vg00
/dev/dsk/c0t6d0


The Volume Group /dev/vg67/group was not matched with any Physical Volumes.
The Volume Group /dev/vg100/group was not matched with any Physical Volumes.
Scan of Physical Volumes Complete.
#

Maybe I'm wrong here, but I thought that the volume groups vg67 and vg100 existed. Maybe not? Well, assuming that, I went to start fresh, beginning with pvcreate.

# pvcreate -f /dev/rdsk/c4t0d1
pvcreate: writing LVM record: Invalid argument

Alright, so I went to try to create vg67 there.

# vgcreate /dev/vg67 /dev/dsk/c4t0d1
Increased the number of physical extents per physical volume to 17346.
vgcreate: IO error on Physical Volume device /dev/dsk/c4t0d1: #

Well, I thought I'd just trash the physical volume.

# pvremove /dev/rdsk/c4t0d1
pvremove: Physical Volume "/dev/rdsk/c4t0d1" contains no LVM information

What is the problem here with my physical volume? Do you know what I need to do in order to rebuild my volume groups? Thanks.

Still truckin',

Melissa

[dhanish]

Hi,
Can u pls try moving the lvmtab and lvmtab.old and doing the vgscan again.

[Eddie Warren]

Hi Melissa,
If the arrays are being shared by both systems, verify the hardware paths are the same. For instance do
"ioscan -fnC disk" on both systems and compare the output. It sounds like when you tried to import the volume group the system did not recognize the hardware path. This would occur
if you did a "vgexport" (created your mapfile and copied it to the system you are doing the vgimport. "The hardware paths would have to be the same on both systems".
Take Care, and good luck.

Eddie

[Melissa Murphy]

Thanks for your suggestions, guys.

I did another mv /etc/lvmtab /etc/lvmtab.old followed by a vgscan -v and here is what I got:

# vgscan -v
Creating "/etc/lvmtab".
vgscan: Couldn't access the list of physical volumes for volume group "/dev/vg00".
vgscan: Couldn't access the list of physical volumes for volume group "/dev/vg67".
vgscan: Couldn't access the list of physical volumes for volume group "/dev/vg100".
Physical Volume "/dev/dsk/c4t0d7" is not part of a Volume Group
Couldn't stat physical volume "/dev/dsk/c2t2d0":
Invalid argument

Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c0t5d0




/dev/vg00
/dev/dsk/c0t6d0


Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c4t0d0


/dev/vg67

vgscan: Quorum not present, or some physical volume(s) are missing.
Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c4t0d1

The Volume Group /dev/vg100/group was not matched with any Physical Volumes.
Scan of Physical Volumes Complete.
*** LVMTAB has been created successfully.
*** If PV links are configured in the system.
*** Do the following to resync information on disk.
*** #1. vgchange -a y
*** #2. lvlnboot -R

Then I tried:

# vgchange -a y
Volume group "/dev/vg00" has been successfully changed.
vgchange: Couldn't activate volume group "/dev/vg67":
Quorum not present, or some physical volume(s) are missing.
# lvlnboot -R
vgcfgbackup: Volume group not activated.
# vgremove vg100
vgremove: Volume group "/dev/vg100" does not exist in the "/etc/lvmtab" file.
vgremove: Couldn't remove volume group "vg100".

So that didn't work out. I never tried vgimports and vgexports like I guess I should have. Right now I can't even remove or recreate any. I looked at the ioscan and the hardware paths were something that I was curious about at one point. Here are portions of ioscan -fnC disk on each computer:

On Lore:

Class I H/W Path Driver S/W State H/W Type Description
==================================================================================
disk 6 10/8.8.0.255.0.0.0 sdisk CLAIMED DEVICE LSI INF-01-00
/dev/dsk/c4t0d0 /dev/rdsk/c4t0d0
disk 8 10/8.8.0.255.0.0.1 sdisk CLAIMED DEVICE LSI INF-01-00
/dev/dsk/c4t0d1 /dev/rdsk/c4t0d1
disk 7 10/8.8.0.255.0.0.7 sdisk CLAIMED DEVICE LSI Universal Xport
/dev/dsk/c4t0d7 /dev/rdsk/c4t0d7
disk 2 10/12/5.2.0 sdisk CLAIMED DEVICE

On Data:

Class I H/W Path Driver S/W State H/W Type Description
==================================================================================
disk 8 8/12.8.0.255.0.2.0 sdisk CLAIMED DEVICE LSI INF-01-00
/dev/dsk/c4t2d0 /dev/rdsk/c4t2d0
disk 9 8/12.8.0.255.0.2.1 sdisk CLAIMED DEVICE LSI INF-01-00
/dev/dsk/c4t2d1 /dev/rdsk/c4t2d1
disk 10 8/12.8.0.255.0.2.7 sdisk CLAIMED DEVICE LSI Universal Xport
/dev/dsk/c4t2d7 /dev/rdsk/c4t2d7

The paths that end in .0 should be the 100GB array and the ones that end in .1 should be the 67GB array. Also, something that's not directly connected, what is the Universal Xport? What is this device? It's not *actually* another disk, is it? Well, what do I do if the hardware paths are not identical on each system?

Thanks again,
Melissa

[Joel Shank · Accepted solution]

Melissa

You need to specify the physical disk devices that are assigned to the volume groups you are trying to import. this means that you need to know which devices on DATA map to the SAME devices on LORE. For example, if vg67 is on c4t0d0 on lore and maps to c4t2d0 on data, then your import would look like this (on data):
vgimport vg67 /dev/dsk/c4t2d0

HTH -- jls