[linux-lvm] vgscan failure after changing SCSI controller

[atark]

Hello,

I moved SCSI controllers around im my server and have lost contact with
my VG.  The VG is on an extrenal array with 6 disks, 4 or which are used
for the VG. Also I've changed back to the original controller
cofiguration. How can I verify if the VG is truly hosed? Tried
vgcfgrestore to no avail.....

Any help is appreciated!

--Andy


vgscan is failing with:

vader root # vgscan -v
vgscan -- removing "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- creating empty "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- scanning for all active volume group(s) first
vgscan -- reading data of volume group "spacevg" from physical volume(s)
vgscan -- ERROR "lv_read_all_lv(): number of LV" can't get data of
volume group "spacevg" from physical volume(s)
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume
group

Here is pvscan:

vader root # pvscan -v
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- walking through all physical volumes found
pvscan -- inactive PV "/dev/scsi/host2/bus0/target1/lun0/disc"  is
associated to unknown VG "spacevg" (run vgscan)
pvscan -- inactive PV "/dev/scsi/host2/bus0/target2/lun0/disc"  is
associated to unknown VG "spacevg" (run vgscan)
pvscan -- inactive PV "/dev/scsi/host2/bus0/target3/lun0/disc"  is
associated to unknown VG "spacevg" (run vgscan)
pvscan -- inactive PV "/dev/scsi/host2/bus0/target4/lun0/disc"  is
associated to unknown VG "spacevg" (run vgscan)
pvscan -- total: 4 [50.79 GB] / in use: 4 [50.79 GB] / in no VG: 0 [0]