LVM and VxVM

"LogicalExtentsNumber" is not bigger than current setting

 
SOLVED
Go to solution
Adeel Zia
Occasional Advisor

"LogicalExtentsNumber" is not bigger than current setting

I tried to extend one of my logical volumes

# lvextend –L 2364 /dev/vg_isre/lv_isre

But I got the following error:
warning: rounding up logical volume size to extent boundary at size "2368" MB.
warning: rounding up logical volume size to extent boundary at size "2560" MB for striping.
lvextend: "LogicalExtentsNumber" is not bigger than current setting.

Nothing changed lv was not extended,current settings for the VG and LV are as follows:

# vgdisplay /dev/vg_isre
--- Volume groups ---
VG Name /dev/vg_isre
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 3
Open LV 3
Max PV 16
Cur PV 4
Act PV 4
Max PE per PV 43594
VGDA 8
PE Size (Mbytes) 64
Total PE 43588
Alloc PE 40628
Free PE 2960
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

# lvdisplay /dev/vg_isre/lv_isre
--- Logical volumes ---
LV Name /dev/vg_isre/lv_isre
VG Name /dev/vg_isre
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule striped
LV Size (Mbytes) 100096
Current LE 1564
Allocated PE 1564
Stripes 4
Stripe Size (Kbytes) 32
Bad block on
Allocation strict
IO Timeout (Seconds) default

I assume the problem lies in "Schedule = striped" in the lvdisplay command.

During some of my research I have noticed the one should have a Mirror/UX utility on the server,currently I don't,but if that helps probably I can manage to get that installed on the server.

Still what is plan of action,and commands required.

Thanks in advance.

7 REPLIES 7
TTr
Honored Contributor
Solution

Re: "LogicalExtentsNumber" is not bigger than current setting

The error message is correct. You need to use "l" (lower case L) to indicate extends in the lvextend command. The "L" is for MB.
Bhadresh
Trusted Contributor

Re: "LogicalExtentsNumber" is not bigger than current setting

Hi,

As earlier told, you have used â L in lvextend command which indicates size in megabytes. Size is rounded up to the nearest multiple of the logical extent size, equivalent to the physical extent size defined for the volume group by the vgcreate command

Have a look at following manual to know more about various options with lvextend:
http://docs.hp.com/en/B2355-60130/lvextend.1M.html

Regards,
Bhadresh
johnsonpk
Honored Contributor

Re: "LogicalExtentsNumber" is not bigger than current setting


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

I guess the error is pretty straight forward
isn't it ?

>> â L 2364 ...You have given the size as 2364 MB

and the current size is 100096 MB..

If you want to extend that lv, give some values greater than 100096 with -L option in lvextend

Regards!
Johnson
nightwich
Valued Contributor

Re: "LogicalExtentsNumber" is not bigger than current setting

Hi Adeel


Your problem was already explain.

What concern to mirror it's always a good practice have mirror.

there are a nice book that you can use to setup mirror.

http://www.google.pt/#hl=pt-PT&source=hp&q=when+good+disks+go+rong&meta=&aq=f&aqi=&aql=&oq=&gs_rfai=&fp=6e42e956d302014d

This came as default in 11iv3.


Regards.
Anoop Sivan
Frequent Advisor

Re: "LogicalExtentsNumber" is not bigger than current setting

Hello Adeel

IF You need to extend "/dev/vg_isre/lv_isre"
LV to further 2364 MB,

# lvextend -L 102460 /dev/vg_isre/lv_isre
Abid Iqbal
Regular Advisor

Re: "LogicalExtentsNumber" is not bigger than current setting

Hi,
This is very simple.
Current LE are 1564, you want to add/extend 800 more PE.
# lvextend -l 2364 /dev/vg_isre/lv_isre
if online jfs is installed.
# fsadm -b 9408M /mount_name
Abid Iqbal
Regular Advisor

Re: "LogicalExtentsNumber" is not bigger than current setting

sorry,
the last line is as under
# fsadm -b 150528M /mount_name
:)