1829087 Members
2451 Online
109986 Solutions
New Discussion

LVM problem

 
hpuxsa
Frequent Advisor

LVM problem

I have a server running 11.11. This is connected to Clariion cx500. It had two luns of 150GB and 190GB each with data on it. I rebooted the server today (this was the first reboot after the luns were configured). When the system came up one of the VG's did not get activated. When I tried to activate manually it complained about qourum. Tried with -q n option VG got activated but could not mount the filesystems.

The disks specified in /etc/lvmtab for the volume group are visible and it shows claimed in ioscan. I can also do a diskinfo and it shows the details. But
lvdisplay -v /dev/cxvg01/lvol1 gives
LE PV1 PE1 Status 1
00000 ??? 00000 current
00001 ??? 00001 current
The PV Name for all lv's comes with ???.

pvdisplay -v /dev/dsk/c7t0d0 gives
CUR LV 0
PE Status LV LE
0000 free 0000
0001 free 0000

Everything was working fine until the reboot. One of the VG is working fine with no problems. Appreciate your help on this.
4 REPLIES 4
RAC_1
Honored Contributor

Re: LVM problem

What error does it give, when you try to mount it?? Does it complain baout fsck?? If yes run fsck on it and try to mount.

Anil
There is no substitute to HARDWORK
hpuxsa
Frequent Advisor

Re: LVM problem

The error while trying to mount is
/dev/cxvg01/lvol1: unrecognized file system

RAC_1
Honored Contributor

Re: LVM problem

Error means, mount can not determine the FS type of this file system.
what is the directive is fstab for this mount point?? Are you sure that you did newfs on this raw vol??
There is no substitute to HARDWORK
Peter Unger
Occasional Advisor

Re: LVM problem

Hi,

I have played a little bit and I've got similiar output :D


# lvdisplay -v /dev/vg00/lvol1
--- Logical volumes ---
LV Name /dev/vg00/lvol1
VG Name /dev/vg00
LV Permission read/write
LV Status available/stale
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 300
Current LE 75
Allocated PE 150
Stripes 0
Stripe Size (Kbytes) 0
Bad block off
Allocation strict/contiguous
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c3t6d0 75 75

--- Logical extents ---
LE PV1 PE1 Status 1 PV2 PE2 Status 2
00000 /dev/dsk/c3t6d0 00000 current ??? 00000 stale
00001 /dev/dsk/c3t6d0 00001 current ??? 00001 stale


###
# vgdisplay -v /dev/vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 8
Open LV 8
Max PV 16
Cur PV 2
Act PV 1
Max PE per PV 2500
VGDA 2
PE Size (Mbytes) 4
Total PE 2168
Alloc PE 1781
Free PE 387
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/stale
LV Size (Mbytes) 300
Current LE 75
Allocated PE 150
Used PV 1
.............................

--- Physical volumes ---
PV Name /dev/dsk/c3t6d0
PV Name /dev/dsk/c3t5d0 Alternate Link
PV Status available
Total PE 2168
Free PE 387
Autoswitch On


### that's not that funny as this one output:

# ioscan -fnkC disk
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 0 10/0/14/0.0.0 sdisk CLAIMED DEVICE Lite-On LTN486 48x Max
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 10/0/15/1.5.0 sdisk CLAIMED DEVICE COMPAQ BD0366459B
/dev/dsk/c3t5d0 /dev/rdsk/c3t5d0
disk 2 10/0/15/1.6.0 sdisk CLAIMED DEVICE QUANTUM ATLAS10K-9LVD
/dev/dsk/c3t6d0 /dev/rdsk/c3t6d0
#

/dev/dsk/c3t5d0 and /dev/dsk/c3t6d0 are totaly different disks!
and vg is thinking that I have one PV with 2 dev files like in SAN :D

how I got this ?
PV was unavailable than I did dd if=/dev/dsk/c3t6d0 of=/dev/dsk/c3t5d0 and than vgchange -a y
:D

I wanted to simulate the state which hpuxsa had :D now the question is: how to get out from this situation :d