LV extend in the VG

[Inesa Clinko]

Please help me in increasing LV in the VG:

The following message occured,when Im trying
to do lvextend:

# lvextend -L 2150000 /dev/fmsvg/fms
Warning: rounding down logical volume size to extent boundary at size "2149984"
MB.
lvextend: "LogicalExtentsNumber" is bigger than the maximum value allowed.

How could I handle this ?

[Pete Randall]

Does the VG have enough free space to accomodate this increase? How about posting the output from vgdisplay?


Pete

[Mobeen_1]

Inesa,
Looks like there is not enough space in the VG to accomodate your LV expansion.

It looks to me like the max you can extend LV is 2149984.

I would suggest that you check and issue the same command again with a different value

regards
Mobeen

[john korterman]

Hi,

apparently you try to use more disk space than available: it would be 2150000 megabytes.
Check first what free space you have available in the VG, e.g. by "vgdisplay -v /dev/vgXX" XX being the number of your volume group. Look for the heading --- Physical volumes ---
and check what it says under Free PE.

The size of the logical volume must be a multiplum of the extent size, hence the mentioning that LVM will round it off.

regards,
John K.

[Marcel Boogert_1]

Hi there,

Have you used the -o option when you created the filesystem. If not use the fsadm command to do so.

MB.

[bhavin asokan]

hi lnesa,

lvextend is having two options to specify the size.

-l if you are using this option you
should specify the number of logical
extents which is more than that of
existing number of physical extents.
you can get the existing number of
extents by lvdisplay of specified LV

note : you can get the no. of free extents and one logical extents size by vgdisplay command of vg which contains the specified LV.total free space=free extents*one extents size.

-L by this option you can specify the size to which the LV is to be extended. pls note that the size to be mentioned in MB (megabytes) not in bytes or kilobytes. the size should be more that current size. get the current size & free size by lvdisplay & vgdisplay commands. refer man page of lvextend for more details,

regds,

[Inesa Clinko]

I found, that I have enough space in VG, but
I have reached the max of LE for LV: 65535.

Could anybody explain me what are the "default", "max" and "reccomended" sizes for different situations for:

LE for VG
PE for VG
and other related values.

What can I choise for these values when Im creating VG,LV and FS

[bhavin asokan]

hi,

the LE size is always equal to PE size .
if you are having large storage space ,you can keep the size of PE=32MB .ie. max size of lv can get up to 32*65535. but it not recomended to create bigger lv's due to performance issues. i think you are having 32 MB LE size.

regds,

[Prashant Zanwar_4]

I agree with Bhavin.
You can do vgdisplay /dev/vgXX. Check for

Free PE
PE Size

Available space = Free PE*PE Size
I dont know how much space you posses on the required VG and how much you need to extend.
Also you can check for max PE per PV, so depending on your valus of PE in MB, you will have the disk size.

There is no question of free LE's, as long as free PE's are there, you can increase the size of LV.

lvextend -L LV_PATH PV_PATH.
Hope this helps.
Prashant

[Todd McDaniel_1]

Inessa,

Could you post your vgdisplay/lvdisplay info? How many FS do you have on this VG? Do you distribute LVOLS across many VGS?

That would help greatly.

2GB of a FS isnt that big, but what is your total allocation for this VG?

You are limited by VG to a max PE of 65535 as stated. The way to manage this is to follow my suggestion: Create a new VG and create this LVOL there.

When I create VGS/LVOLS I make as many VGs as I need and keep them relatively the same size....

In fact, I would also make sure your MAXVGS is set above the default of 32/64. I raise mine to 128 or 256 just so I never have to worry about that.


IF possible make a new VG/LVOL for this /dev/fmsvg/fms...

It is your only choice other than increasing the PE value again, which would include backing up and totally recreating the VG you are in currently which is VG fmsvg. Which I am sure would be a lot of work.

I would suggest making new VGs each time you create new File systems...