SOLVED
Hello Yurub,
You need to use the command "vgmodify" to use the added to the disk, by adding new disks to the logical drive .
When a LUN is dynamically grown (DLE - Dynamic Lun Expansion - at the storage end , here at RAID) , vgmodify should be used to allow LVM to access this new space.
Once the volume group has been adjusted by vgmodify the new space can be allocated using the normal LVM method by lvextend or lvcreate.
You may need to use the command # vgmodify -v -r -a -E vg_name --> review mode , make sure that it is showing new disk size in output .
Now run without -r to make actual changes .
You may refer the White paper "Using the vgmodify command to perform LVM Volume Group Dynamic LUN Expansion (DLE) and Contraction (DLC)" from URL given below for more informaiton .
Section "Dynamic LUN expansion (DLE) and dynamic LUN contraction (DLC)" , page #6 onwards .
https://community.hpe.com/hpeb/attachments/hpeb/itrc-156/377793/1/356848.pdf
Please make sure you have good data backup before making any changes .
I work for HPE/ I am an HPE Employee (HPE Community)
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Hello,
Let us know if you were able to resolve the issue.
If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.
Please click on "Thumbs Up/Kudo" icon to give a "Kudo".
Hello Yurub,
I had a look at the configuration of the vg and it seems it is hitting a limit "Max PV Size (Tbytes)" of 2TB for vg with version 1 .
You could check the limits of different vg versions using # lvmadm -t . Below are the limits for vg version 1.0 which you have .
# lvmadm -t
--- LVM Limits ---
VG Version 1.0
Max VG Size (Tbytes) 510
Max LV Size (Tbytes) 16
Max PV Size (Tbytes) 2 =====>
Max VGs 256
Max LVs 255
Max PVs 255
Max Mirrors 2
Max Stripes 255
Max Stripe Size (Kbytes) 32768
Max LXs per LV 65535
Max PXs per PV 65535
Max Extent Size (Mbytes) 256
As per the table , the max size a disk can have is 2 TB .
The initial size of the disk (before adding new disks) was 2560000MB = 2500GB , which itself was above the limit .
After adding those 2 disks , the new size is 3072000 , ~3000GB which cannot be used in vg with version 1.0 .
****-DB3#vgdisplay vgora
--- Volume groups ---
VG Name /dev/vgora
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 3
Open LV 3
Max PV 6
Cur PV 1
Act PV 1
...
Total PVG 1
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0 ==>
You have 2 options available ,
1)migrate the vg version from 1.0 to 2.x which will accommodate disks with higher size up to 16 TB , use the new size with help of vgmodify as shared earlier or 2) take data backup , recreate the array in such a way that there would be multiple logical volumes with size less than 2 tb so that all of these disks together can use be used make vg with version 1.0 and use all of the space .
You may refer #man vgversion for more information also make sure you have a good data backup before making any changes.
I work for HPE/ I am an HPE Employee (HPE Community)
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Hello Yurub,
The command is vgversion , which will help you migrate vg with version 1.0 to 2.x . There are multiple versions available such as 2.0 / 2.1 and 2.2 .
For example ,
Change the version of a volume group named /dev/vg01 to volume group
version 2.2 and be verbose:
vgversion -v -V 2.2 /dev/vg01
Please refer # man vgversion for more details / steps . also refer #lanadm -t for limits of each version .
I work for HPE/ I am an HPE Employee (HPE Community)
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Hello Yurub,
It seems like 50 gb is taken from each disk for raid - could be for parity writing , thus not available for user .
The size mentioned when the RAID has 10 disks was 2560000 MB .
Ideally, the size should be 600 (disk size) * 10 (no of disks) * 1024 (in MB) / 2 (since it is RAID10 - mirroring) = 3072000.
But the size available is 2560000 as shown below .
---------- LOGICAL DRIVE 0 ----------
Device File = /dev/dsk/c4t0d0
RAID Level = 1+0
Size = 2560000 MB ==>
Stripe Size = 128 KB
Status = OK
Thus we have almost 512000 MB (3072000 - 2560000)which is ~ 500GB missing when you have RAID with 10 disks configured .
So for a single disk it is 50gb (500gb/10 disks) non-usable for data writing .
When you added 2 new disks , the ideal size should be 600 * 12 * 1024 /2 = 3686400 MB ~ 3600GB .
But the current size is 3072000 MB .
---------- LOGICAL DRIVE 0 ----------
Device File = /dev/dsk/c4t0d0
RAID Level = 1+0
Size = 3072000 MB ==>
Stripe Size = 128 KB
Status = OK
So the missing size is again 3686400 - 3072000 = 614400 MB , ~ 600gb .
Which is nothing but addition of 100gb tp previous missing size (500gb) , 50 gb from each disk , thus 100gb for 2 new disks .
Hope this explains .
I work for HPE/ I am an HPE Employee (HPE Community)
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]