topic Re: lvextend in Operating System - HP-UX

lvextend

Ragni Singh — Thu, 22 Aug 2002 15:14:47 GMT

Hey all,

I need to extend the file-system to 1gig and when I ran the lvextend -L 1024 /dev/vg00/lvol8, I get this error.

lvextend: "LogicalExtentsNumber" is not bigger than current setting.

Doing my vgdisplay shows the following information...
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 11
Open LV 11
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4350
VGDA 2
PE Size (Mbytes) 4
Total PE 4340
Alloc PE 4065
Free PE 275
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

Please help. Points will be given.

Re: lvextend

Patrick Wallek — Thu, 22 Aug 2002 15:19:26 GMT

That error is saying that vg00/lvol8 is already at 1024MB or more.

If you do a 'vgdisplay -v vg00' and look at the info for lvol8, how many extents are allocated? Take that number and multiply by 4 and you get the # of MB that lvol8 is currently. I will bet that it is larger than 1024.

To fix the error you are getting, pick a number that is larger than the current size of lvol8.

Re: lvextend

Jean-Luc Oudart — Thu, 22 Aug 2002 15:21:18 GMT

You want to give the new size not the increase.
cf lvextend man pages

Jean-Luc

Re: lvextend

A. Clay Stephenson — Thu, 22 Aug 2002 15:22:35 GMT

It appears that lvol8 is already at least 1024MB. Do a vgdisplay -v /dev/vg00 and let's see how big the LVOL's are.

Re: lvextend

Sajid_1 — Thu, 22 Aug 2002 15:22:54 GMT

Are you using '-l' or '-L' ? what about the LVM patches?

Re: lvextend

S.K. Chan — Thu, 22 Aug 2002 15:24:34 GMT

The current size of lvol8 is equal or more than 1024MB, that's why you're getting the error. You have 275x4=1100MB ie about 1.1GB of free extents available in vg00. So when you extent lvol8, just make sure you do not extent it by more than 1.1GB. For example ..
# lvextend -L 1800 /dev/vg00/lvol8
would be fine ... (new size is 1.8GB)

Re: lvextend

Sajid_1 — Thu, 22 Aug 2002 15:25:19 GMT

Try this command:
# lvdisplay -v /dev/vg00/lvol8

This will tell you the LV details and size. For increasing it to 2GB:

# lvextend -L 2048 /dev/vg00/rlvol8

Re: lvextend

MANOJ SRIVASTAVA — Thu, 22 Aug 2002 15:27:02 GMT

lvextend: "LogicalExtentsNumber" is not bigger than current setting.

what is the current size , if you are increasing it by 1.gb then do a lvexnted -L 2048 /dev/vg00/lvol8

Alternatively use SAM

Manoj Srivastava

Re: lvextend

Sajid_1 — Thu, 22 Aug 2002 17:23:59 GMT

hello,

If you still have the problem and if you are running 10.20, then install this patch - PHCO_23427. This is the LVM cumulative patch and will eliminate errors of lvextend when using -L.

hth,

Re: lvextend

Martin Burnett_2 — Thu, 22 Aug 2002 17:48:09 GMT

Hello,

From your original output really doesn't help because we need to see the lvdisplay output as well. For instance:

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

In this logical volume it shows:
Allocated PE =35

Take this and the original output you posted from the vgdisplay which showed:

PE Size (Mbytes) 4

So 500 x 4= 2000 which is displayed as:
LV Size 2000

So if I ran your command on this logical volume I would receive the same kind of error because my logical extents would be less than what I have configured already.

lvextend can be used with lower case "-l" which will specify size using extents. This is more accurate than using the upper case "-L" which specifies size in MB. The "-l" option will round the size off to the nearest whole extent value.

Thanks for participating in the forums,

Martin
Chaos reigns within. Reflect, repent, and reboot. Order shall return.