Re: Problem with VG01

 
Lucent
Occasional Advisor

Problem with VG01

hi,

on our L1000 (B 11.0), I created a Volume group vg01 with 2 physical Volumes (/dev/dsk/c5t8d0 and /dev/dsk/c4t8d0) but the first physical volume is not displayed with the command vgdisplay.

Hereafter some commands that I executed


nmc2tcsb,gadmin,axadmin # vgdisplay -v vg01

--- Volume groups ---
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 3
Open LV 3
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 8683
VGDA 2
PE Size (Mbytes) 4
Total PE 8681
Alloc PE 8553
Free PE 128
Total PVG 1
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg01/lvol6
LV Status available/syncd
LV Size (Mbytes) 1000
Current LE 250
Allocated PE 250
Used PV 1

LV Name /dev/vg01/lvol9
LV Status available/syncd
LV Size (Mbytes) 18000
Current LE 4500
Allocated PE 4500
Used PV 1

LV Name /dev/vg01/lvol3
LV Status available/syncd
LV Size (Mbytes) 15212
Current LE 3803
Allocated PE 3803
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c4t8d0
PV Status available
Total PE 8681
Free PE 128
Autoswitch On


--- Physical volume groups ---
PVG Name PVG01_NOR
PV Name /dev/dsk/c4t8d0



# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 0 0/0/1/0.1.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
disk 1 0/0/1/1.2.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 2 0/0/2/0.2.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
disk 3 0/3/0/0.8.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c4t8d0 /dev/rdsk/c4t8d0
disk 4 0/7/0/0.8.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c5t8d0 /dev/rdsk/c5t8d0




nmc2tcsb,sys,root # diskinfo /dev/rdsk/c5t8d0
SCSI describe of /dev/rdsk/c5t8d0:
vendor: FUJITSU
product id: MAJ3364MC
type: direct access
size: 35566480 Kbytes
bytes per sector: 512
nmc2tcsb,sys,root #


# strings /etc/lvmtab
/dev/vg00
]>Gs
/dev/dsk/c1t2d0
/dev/dsk/c2t2d0
/dev/vg01
/dev/dsk/c4t8d0
/dev/dsk/c5t8d0



nmc2tcsb,sys,root # vgscan
vgscan: The physical volume "/dev/dsk/c1t2d0" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c2t2d0" is already recorded in the "/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c4t8d0" is already recorded in the "/etc/lvmtab" file.

Couldn't stat physical volume "/dev/dsk/c0t1d0":
Invalid argument


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/vg01 failed.
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/c5t8d0

nmc2tcsb,sys,root #
nmc2tcsb,sys,root #

script done on Mon Nov 8 14:05:08 2004


thinks for your hel
4 REPLIES 4
Sunil Sharma_1
Honored Contributor

Re: Problem with VG01

I believe you have only one physical volume in vg01 but it has two path. primery and alternate. try to run command.

#vgextend vg01 /dev/dsk/c5t8d0
the run vgdusplay and post the output og vgdisplay -v here.


Sunil
*** Dream as if you'll live forever. Live as if you'll die today ***
SYS ADMIN_7
Advisor

Re: Problem with VG01

Hi

Please post the command used.
try creating the new lvmtab file as follows
#mv /etc/lvmtab /etc/lvmtab.ori
#vgscan -av

This will create new vgscan.

Otherwise as mentioned in other post, it may be alternative path.

Rgds
Suraj
Fred Ruffet
Honored Contributor

Re: Problem with VG01

If it were alternate link, it would be displayed in "vgdisplay -v". Rename /etc/lvmtab and rerun a "vgscan -av". Post output from this last command, from a new "ioscan -C disk", "vgdisplay -v" and new /etc/lvmtab.

Regards,

Fred
--

"Reality is just a point of view." (P. K. D.)
Tim D Fulford
Honored Contributor

Re: Problem with VG01

/dev/dsk/c5t8d0 already belongs to a volume group.... and LVM does not think it is vg01.... It may well be that
o c5t8d0 is malfunctionining and does belong to vg01, but LVM is having problems using it.
o c5t8d0 is in another volume group, and somehow you have the same minor number as vg01.

Basically there is probably a problem here.

- post "strings /etc/lvmtab"
- use mstm & look at the disk & see if there are any errors
- look in syslog.log and seeif there are any POWERFAIL messages

Regards

Tim

-