FS extension

[kgpenator]

Hi Every one,

   I am in need to increase four FS which will come under one VG(VG consists of 4 LV).As per storage team policy they will provide  LUN's in each size of 8GB.It's multipathing LUN's so they will give 2 PV instead of one 1PV.Each LV size has to be increased up to 585GB .How many LUN's needed to complete this? I s there anything to be noted before increase LV "Schedule parallel"?

xyzabc# lvdisplay /dev/vg04scq/lv1
--- Logical volumes ---
LV Name /dev/vg04scq/lv1
VG Name /dev/vg04scq
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 510800
Current LE 31925
Allocated PE 31925
Stripes 0
Stripe Size (Kbytes) 0
Bad block NONE
Allocation PVG-strict/distributed
IO Timeout (Seconds) default

xyzabc# vgdisplay /dev/vg04scq
--- Volume groups ---
VG Name /dev/vg04scq
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 4
Open LV 4
Max PV 250
Cur PV 128
Act PV 128
Max PE per PV 1016
VGDA 256
PE Size (Mbytes) 16
Total PE 130048
Alloc PE 127700
Free PE 2348
Total PVG 2
Total Spare PVs 0
Total Spare PVs in use 0

[Stephan.]

That will not work ...

Max PV 250
Cur PV 128

leave a maximum of 122 PV's for extension, with 8 GB in size this will be a max increase of 976 GB for that VG. With the requirement of 4 x 585 GB you want to increase to 2340 GB  (498,828125 GB exist in lv1).

[Patrick Wallek · Accepted solution]

@ Stephan -- I read the problem that each LUN needs to increased so it is 585 GB in size.  Not increased BY 585 GB.

585 GB = Roughly 585,000 MB.  Your current LV appears to 510 GB, so you need to increase by 75 GB.  For 75 GB, you would need (75 / 8 = 9.375 LUNs) 10 LUNs of 8 GB size. 

If all 4 of your LVs are the same size, then you need an additional 300 GB of disk space, which would equate to (300 / 8 = 37.5 LUNs) 38 LUNs.

If you want to keep each set of LUNs separate for each LV, you would need 40 LUNs.

[Stephan.]

Hmm after reading it again possible that you are right, but it is not really clear to me due to the missing information of lv2-4

I would prefer an 'vgdisplay -v vg00' to verify.

[kgpenator]

Hi Stephen,

Here i am attaching the output of vgdisplay -v /dev/vg04scq  .

Kindly revert back as soon as possible.

Thanks for yours reply

[Stephan.]

Thanks, in this case Patrick provided the correct answer.

All your LVs are ~ 500GB and you want to extend to 585 GB  (+ 85GB) using 8GB LUNs, this means 11 LUNs per LV = 44 LUNs

Kudos should go to Patrick.

[kgpenator]

Further i am adding this LUN's like this,

1.pvcreate /PV

2.vgextend /dev/vg04xx

3.lvextend -L LV

4.fsadm -F vxfs -bM /filesystem

Correct me if i am wrong

[Patrick Wallek]

Yes, your steps look good!

[kgpenator]

No . it didn't worked as it was mentioned above.
i used vgextend -g PVG_Name /dev/vg04xx xxx xxx
because of Allocation PVG-strict/distributed policy

[Torsten.]

>> i used vgextend -g PVG_Name /dev/vg04xx xxx xxx

What was the exact command?

Did you adjust the PVG file?

[kgpenator]

xxxxx# lvdisplay /dev/vg04bwq/lv1
--- Logical volumes ---
LV Name /dev/vg04bwq/lv1
VG Name /dev/vg04bwq
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 677264
Current LE 42329
Allocated PE 42329
Stripes 0
Stripe Size (Kbytes) 0
Bad block NONE
Allocation PVG-strict/distributed
IO Timeout (Seconds) default

xxxxxx# vf gdisplay /dev/vg04bwq
--- Volume groups ---
VG Name /dev/vg04bwq
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 4
Open LV 4
Max PV 250
Cur PV 176
Act PV 176
Max PE per PV 1016
VGDA 352
PE Size (Mbytes) 16
Total PE 178816
Alloc PE 169316
Free PE 9500
Total PVG 1
Total Spare PVs 0
Total Spare PVs in use 0

xxxxx# lvextend -L 748944 /dev/vg04bwq/lv1
lvextend: Not enough free physical extents available.
Logical volume "/dev/vg04bwq/lv1" could not be extended.

I have face this error.Due to PVG restriction policy.Luckily it was the free volume,so i did 

xxxxx# lvreduce -L 677264 /dev/vg04bwq/lv1
When a logical volume is reduced useful data might get lost;
do you really want the command to proceed (y/n) : y
Logical volume "/dev/vg04bwq/lv1" has been successfully reduced.

xxxxx# vgreduce  -l /dev/vg04bwq /dev/dsk/c46t6d1 /dev/dsk/c47t6d1
Device file path "/dev/dsk/c46t6d1" is an primary link.
Removing primary link and switching to an alternate link.
Device file path "/dev/dsk/c47t6d1" is an alternate path.
Volume group "/dev/vg04bwq" has been successfully reduced.
Volume Group configuration for /dev/vg04bwq has been saved in /etc/lvmconf/vg04bwq.conf

xxxxxx#vgextend -g pvg _vg04bwq_ /dev/vg04bwq /dev/dsk/c46t6d1 /dev/dsk/c47t6d1

vgextend: Warning: Max_PE_per_PV for the volume group (1016) too small for this PV (1049).
Using only 1016 PEs from this physical volume.
Volume group "/dev/vg04bwq" has been successfully extended.
Physical volume group "pvg_vg04bwq_" has been successfully extended.
Volume Group configuration for /dev/vg04bwq has been saved in /etc/lvmconf/vg04bwq.conf

xxxxxx# VG  vgdisplay /dev/vg04bwq
--- Volume groups ---
VG Name /dev/vg04bwq
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 4
Open LV 4
Max PV 250
Cur PV 188
Act PV 188
Max PE per PV 1016
VGDA 376
PE Size (Mbytes) 16
Total PE 191008
Alloc PE 169316
Free PE 21692
Total PVG 2
Total Spare PVs 0
Total Spare PVs in use 0

xxxxx# lvextend -L 747264 /dev/vg04bwq/lv1
Logical volume "/dev/vg04bwq/lv1" has been successfully extended.
Volume Group configuration for /dev/vg04bwq has been saved in /etc/lvmconf/vg04bwq.conf

xxxxx# fsadm -F vxfs -b 747264M /oracle/BWQ/sapdata1
vxfs fsadm: /dev/vg04bwq/rlv1 is currently 693518336 sectors - size will be increased

It worked 

[kgpenator]

I didn't adjusted PVG file?Could you post how to do on that way?