Disk space pbm

[madhu_11]

I am having one 36 GB hdd. I already configured lvol3 (8290MB),lvol1(298MB),lvol4(204MB),lvol5(5120MB) and lvol6(10633MB). i am having around 9600 mb free space on this hdd.
i am not able to use this space.If we are seeing PVDISPLAY -v /dev/dsk/c0t0d0 , it showing that no free PE avilable.All the 4374 PVs are allocated. Further i am seeing ??? instead of /dev/vg00/lvol? starting from PE 1171 to 2450.


regards

Madhu Gopalakrishnan

MY os is 11.0 and server is D380.

Any one help me use this free space w/o recreating PV.

[Pete Randall]

What is the PE size shown by vgdisplay?


Pete

[Steven E. Protter]

Have you accounted for swap?

It must be using some space.

Run swapinfo -tam.

I have approximzately 30 GB of space based on your figures. There should be 6 GB left, except the usual location of swap is /dev/vg00/lvol2

Also, the Volume Group may not be able to use all available disk space.

This should have been accounted for at install time, but if you did a disk upgrade and restored with Ignite, the Volume group may not be able to use all the Physical extents.


Run and post this:
vgdisplay /dev/vg00

That would help.

SEP

[Pete Randall]

And the max PE per PV?


Pete

[Sridhar Bhaskarla]

Hi Madhu,

This would happen if someone did "rm /dev/vg00/lvolx" instead of "lvremove /dev/vg00/lvolx".

Do a "vgdisplay -v vg00 |grep "LV Name"" and compare the lvols against what you have in /dev/vg00

Find out the missing "minor number". of the lvols in /dev/vg00. You can do it by "ll /dev/vg00/r*" and observe the 0x00000x". They should be sequential. Say "1-9". Say if you don't find "7", then it was logical volume that got removed. You can recreate it by using mknod command.

#mknod /dev/vg00/lvol7 b 64 0x000007
#mknod /dev/vg00/rlvol7 c 64 0x000007

If you do a pvdisplay now, lvol7 should show up instead of ???s.

If you don't have break in the sequence, then create the device files with the next number in the sequence. In the example I gave, it would be a (next to 9).

#mknod /dev/vg00/lvol10 b 64 0x00000a
#mknod /dev/vg00/rlvol10 c 64 0x00000a

-Sri

[Pete Randall]

The minor number is specified as 0x0n0000, I believe, where n is the minor number.


Pete

[James R. Ferguson]

Hi:

Sri has the most logical explanation for what you see.

With regard to the minor number, he is correct. The device file for 'lvol1' on 'vg03' would look like:

brw-r----- 1 root sys 64 0x030001 Jun 17 15:58 lvol1

Regards!

...JRF...

[Pete Randall]

Thanks again, James. I was thinking of the minor number for the VG.


Pete

[James R. Ferguson]

Hi Pete:

No problem. I too had to look twice, since the device files are for vg00. :-))

Regards!

...JRF...