cancel
Showing results for 
Search instead for 
Did you mean: 

lvextend stripped disks

Duffs
Regular Advisor

lvextend stripped disks

Hi,
I have created a new vg (vg01) which consists of one large lv stripped across 14x73G disks.

As can be seen from the output below the diskspace is only allocating a fraction of the space to the lv. I have tried to extend this but recieve the following error (below). Any ideas?? I want to allocate all the diskspace to the lv.

# vgdisplay vg01
--- Volume groups ---
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 14
Act PV 14
Max PE per PV 8750
VGDA 28
PE Size (Mbytes) 8
Total PE 122486
Alloc PE 15316
Free PE 107170
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0


# lvdisplay /dev/vg01/lvol1
--- Logical volumes ---
LV Name /dev/vg01/lvol1
VG Name /dev/vg01
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule striped
LV Size (Mbytes) 122528
Current LE 15316
Allocated PE 15316
Stripes 14
Stripe Size (Kbytes) 64
Bad block on
Allocation strict
IO Timeout (Seconds) default


# lvextend -L 979888 /dev/vg01/lvol1
lvextend: "LogicalExtentsNumber" is bigger than the maximum value allowed.
9 REPLIES
Antonio Cardoso_1
Trusted Contributor

Re: lvextend stripped disks

Hemmetter
Esteemed Contributor

Re: lvextend stripped disks

Hi Duffs

try to
lvextend -l 122486 /dev/vg01/lvol1

rgds
HGH
Robert-Jan Goossens_1
Honored Contributor

Re: lvextend stripped disks

Hi Duffs,

PE Size (Mbytes) 8
Free PE 107170

8 X 107170 = 857360

# lvextend -L 857360 /dev/vg01/lvol1

Regards,
Robert-Jan
Sivakumar TS
Honored Contributor

Re: lvextend stripped disks


Hi,

with lvextend, It is always

-l --> interms of extents

-L --> interms of MB

Regards,

Siva.

Nothing is Impossible !
Sivakumar TS
Honored Contributor

Re: lvextend stripped disks

In our case,

we have

Free PE 107170

and PE size 8MB

hence max free space is 857360 MB
Nothing is Impossible !
Duffs
Regular Advisor

Re: lvextend stripped disks

Hi,

I appreciate the feedback back but unfortunately its not any help.

Hemmetter, this is an invalid command.

Robert, you have just replicated the I issue I have outlined; i.e.
lvextend -L 857360 /dev/vg01/lvol1
lvextend: "LogicalExtentsNumber" is bigger than the maximum value allowed.

Duffs
Robert-Jan Goossens_1
Honored Contributor

Re: lvextend stripped disks

man lvextend -L option

Increase the space allocated to the logical volume, specified in megabytes. lv_size is a decimal value greater than the current logical volume size, in the range 1 to 16777216 (the implementation limit). lv_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 (see vgcreate(1M)).

lvextend -L 857360 /dev/vg01/lvol1 is the exact limit!

Try to use 857353 or 857352.

Regards,
Robert-Jan
Prashant Zanwar_4
Respected Contributor

Re: lvextend stripped disks

do a bc -l like following -

echo "107170 * 8" | bc -l
857360
Which is nothing but:

(FREE PE * PE SIZE ) & use this value to extend your LV

lvextend -L 857360 /dev/vgname/lvname

Hope it helps..
Gud luk
Prashant



"Intellect distinguishes between the possible and the impossible; reason distinguishes between the sensible and the senseless. Even the possible can be senseless."
Duffs
Regular Advisor

Re: lvextend stripped disks

Hi,

Ok I have discovered what the problem.

Max PE per PV needed to be increased. The PE's were maxed at approx 60G which ment that it was utilizing the full use of diskspace available to it but not all of the extents were being allocated to each disk, therefore it was falling short of its max.

I needed to blow the vg away and recreate it using the -e option to increase the max number of PE's allocated to each PV.

Rgds,
Duffs