Missing LV (2)

[Carlos Fernandez Riera]

vgdisplay -v | grep "Cur LV"
Cur LV 16

vgdisplay -v | grep -c "LV Name"
15


All LV are mirrored, and Allocated PE is double of Current LE.

Disk space shows differences :
PV Name /dev/dsk/c1t6d0
PV Status available
Total PE 4340
Free PE 1371
Autoswitch On

PV Name /dev/dsk/c2t6d0
PV Status available
Total PE 4340
Free PE 1389
Autoswitch On


And :

lvol3 is minor 10
no minor 03.



Do you know where could be my lvol?.

PS: Volker: the previous question have been missing too. Maybe i am the cause.

[Volker Borowski]

Hi Carlos,

ya, the question disappeard, the "recent responses" link in my profile is corrupted.
Do not know what happened to the first thread.

Did you check, if all your mirrors are OK ?

May be a block went bad, has been tagged dirty by the drive, and therefore the corresponding lvol was set inactive or so.

I guess it would be best, I we could have the entire "vgdisply -v /dev/vg00" output. And check the syslog for some disk-related messages.

Hope this helps
Volker

[Carlos Fernandez Riera]

Hi Volker:

I think lvol of minor 3 is configured, but even if i do a vgexport -m /tmp/map.1 -p /dev/vg00:

1 lvol1
2 lvol2
16 lvol3
4 lvol4
5 lvol5
6 lvol6
7 lvol7
8 lvol8
9 lvolsave
10 lvolswap2
11 lvolswap3
12 lvolswap4
13 lvolcrash
14 lvol14
15 lvol15

There is not minor 3.

I will check syslog. Thanks.

[Shahul]

Hi

Did U checked up the out put of vgdisplay?

#vgdisplay -v /dev/vg00 |pg

Here it will show how many lvols are created and their names. Count those manually and compare. Do a bdf and check for all lvols, whether they are mounted or not. primary swap and boot lvols U will not be able to see.

Best of luck
Shahul

[Santosh Nair_1]

Carlos,

Oddly enough I had the same problem on a system. It turned out that the block device for the lvol was missing, i.e. in my case it was lvol1. The rlvol1 character device was there, but the lvol1 block device wasn't. Also, in my vgdisplay output, the Cur LV and Open LV differd by one. But once I added the block device, everything was back in synch.

Hope this helps.

-Santosh

[Samir Mehta]

Hi,
Do 'vgdisplay -v and check for the following.
1. Cur LV and Open LV
2. Cur PV and Active PV
If you see any mismatch in any of those, then you have a problem. If you see mismatch in the first thing, then do,
lvchange -a y
To find the missing LV, compare vgdisplay LV list with the vgexport -p -m /tmp/lvlist output.

If u see any mismatch in the second stuff, then one of the PVs are powered off, or not working in the system.

Samir

[Carlos Fernandez Riera]

pvdisplay -v /dev/dsk/.....:


0155 current /dev/vg00/lvol3 0016
0156 current /dev/vg00/lvol3 0017
0157 current ??? 0000
0158 current ??? 0001
0159 current ??? 0002
0160 current ??? 0003
0161 current ??? 0004
0162 current ??? 0005
0163 current ??? 0006
0164 current ??? 0007
0165 current ??? 0008
0166 current ??? 0009
0167 current ??? 0010
0168 current ??? 0011
0169 current ??? 0012
0170 current ??? 0013
0171 current ??? 0014
0172 current ??? 0015
0173 current ??? 0016
0174 current ??? 0017
0175 current /dev/vg00/lvol4 0000
0176 current /dev/vg00/lvol4 0001

These are the missing extents..., but:
1- I guess they are from minor 3 ( usually /)
2- I guess they were forgotten by lvmerge (?)
3- I guess vgisplay must display them as unreferenced, and show it minor.

What i must do now:
a) mknod c lvmissing 64 0x000003
b) vgimport -p /dev/dsk/....
c) ????

I apologize show information bite by bite ; i am sending info as i am going foward.

[Santosh Nair_1]

Carol,

I don't believe you need to do anything other than to create the block device. After that, pvdisplay should replace the ?? with the block device that you just created.

-Santosh

[Santosh Nair_1]

Opps...I meant Carlos not Carol...sorry for the typo.

-Santosh

[Carlos Fernandez Riera]

Shantos:

Finally i've created minor 3 as lvmissing and now vgdisplay shows 16 lvols.

This is a easy solution. Now think about a large vg , where you were missing a lvol. How minor you were use?.

[Santosh Nair_1 · Accepted solution]

carlos,

I'm sorry, I didn't understand the question...are you asking how many minor numbers I was using in the VG?

This was a problem that I saw on a workstation which had 4 LVs in the VG...so not really a large VG.

-Santosh

[Carlos Fernandez Riera]

Thanks all for your help.

Volker:

No errros found on syslog neither dmesg -.

Shaul:

Count it manually was done, and it was 15, so i run grep -c "LV Name". Some times i dont know count neither type.

Samir:

Vgexport do not show missing lv.

And i cannot run lvchange -a y for a unknown lvol.



Thanks a lot again.

[Volker Borowski]

Hi Carlos,

did you check /etc/fstab against bdf and vgdisplay -v to track down what is missing ?

If you have nor raw devices for database use, the missing lvol should be listed in /etc/fstab as a filesystem or a swap container.

Having an lvol3 on minor 16 could be due to a drop and a recreated volume.

Volker

[Carlos Fernandez Riera]

The problem, as said Santosh, is a missing special file ( /dev/vg00/xxxx with minor 3).

As long it dont exist on /dev/vg00, all tools from LVM seems to ignore that configured space.

Santosh:

I've assinged 9 points to a clarification. So i think assing new 9 points to the correct respose is a great amount of point. I hope you'll understand.