SLES 10 SP4 system capacity can not exceed LV 1T

SLES 10 SP4 system LV needs expansion.
VG still remaining capacity 120G, but these can not be assigned to a 900G capacity is in the LV.
When prompted expansion LV, LV maximum capacity of 1T.
How to solve this problem?

=================vg information===================
VG #PV #LV #SN Attr VSize VFree
datavg 15 9 0 wz–n- 1.46T 122.00G
=================vg detail information===================
— Volume group —
VG Name datavg
System ID
Format lvm2
Metadata Areas 15
Metadata Sequence No 30
VG Access read/write
VG Status resizable
Cur LV 9
Open LV 9
Max PV 0
Cur PV 15
Act PV 15
VG Size 1.46 TB
PE Size 4.00 MB
Total PE 384000
Alloc PE / Size 352768 / 1.35 TB
Free PE / Size 31232 / 122.00 GB
VG UUID ImxEpJ-y0c4-d2xs-2EAt-eQF0-UBaU-GF2W2P
=================lv information===================
LV VG Attr LSize Origin Snap% Move Log Copy%
ldatalv datavg -wi-ao 998.00G
— Logical volume —
LV Name /dev/datavg/ldatalv
VG Name datavg
LV UUID Fmok2p-YDaD-YqjU-b9ax-3XZM-N2eZ-x1THww
LV Write Access read/write
LV Status available

open 2

LV Size 998.00 GB
Current LE 255488
Segments 12
Allocation inherit
Read ahead sectors 0
Block device 253:12

if you try to resize LV (f.e add 10 gb to it) via

lvextend -L+10G /dev/datavg/ldatalv

what error you get?


Hi andyleigood,

According to the FAQ, your kernel should support a larger size. From :

[QUOTE]4.1.13. What is the maximum size of a single LV? The answer to this question depends upon the CPU architecture of your computer and the kernel you are a running:

[*] For 2.4 based kernels, the maximum LV size is 2TB. For some older kernels, however, the limit was 1TB due to signedness problems in the block layer. Red Hat Enterprise Linux 3 Update 5 has fixes to allow the full 2TB LVs. Consult your distribution for more information in this regard.

[*] For 32-bit CPUs on 2.6 kernels, the maximum LV size is 16TB.

[*] For 64-bit CPUs on 2.6 kernels, the maximum LV size is 8EB. (Yes, that is a very large number.)


SLES10SP4 is pretty old, but typically runs some version of the 2.6 kernel. Do you have extended support for that installation? Then opening a service request might get you information on specific limits of the actual kernel/LVM versions used in your installation.

What are the exact messages you get? A “cut&paste” output showing the command invocation plus the resulting messages of the actually failing run usually are most helpful for others.


When using yast online expansion lv space, as prompted max = 1T.

Hi andyleigood,

have you tried expanding it via command line tools? Else I recommend to open a service request, to get an explanation from engineering for that limit.


Good advice.
I’ll use command to extend LV volunme.