Cannot extend logical volume


 
Thread Tools Search this Thread
Operating Systems AIX Cannot extend logical volume
# 1  
Old 11-23-2016
Cannot extend logical volume

Dear All,

We have an Oracle running on AIX 6.1, now there have an disk spaces issue and we found that we cannot perform to extend the logical volume. Could help to review and make some suggestions.

Status:
we already provisioned some disks to the host, new disks can be scan and add into the volume group, issue just happened during extend the logical volume.

we try to use chlv -x 72174 oravol used PP is 63984, new PP is 8190.

Is that related to the policy "striped" not "parallel"?

Thanks.

Code:
# lslv oravol
LOGICAL VOLUME:     oravol               VOLUME GROUP:   datavg
LV IDENTIFIER:      0006afbb0000d40000000141a0c9e1da.1 PERMISSION:     read/write
VG STATE:           active/complete        LV STATE:       opened/syncd
TYPE:               jfs2                   WRITE VERIFY:   off
MAX LPs:            68847                  PP SIZE:        128 megabyte(s)
COPIES:             1                      SCHED POLICY:   striped
LPs:                63984                  PPs:            63984
STALE PPs:          0                      BB POLICY:      relocatable
INTER-POLICY:       maximum                RELOCATABLE:    no
INTRA-POLICY:       middle                 UPPER BOUND:    16
MOUNT POINT:        /oradata         LABEL:          /oradata
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes (superstrict)
Serialize IO ?:     NO
STRIPE WIDTH:       16
STRIPE SIZE:        64k

The new disks is hdiskpower33 and hdiskpower34
Code:
# lspv |grep datavg
hdiskpower5     0006afbb58e1bb54                    datavg          concurrent
hdiskpower6     0006afbb58ddca06                    datavg          concurrent
hdiskpower7     0006afbb58e8aa28                    datavg          concurrent
hdiskpower8     0006afbb58e44ce2                    datavg          concurrent
hdiskpower10    0006afbb58dfe7b1                    datavg          concurrent
hdiskpower11    0006afbb58eae332                    datavg          concurrent
hdiskpower12    0006afbb58e67454                    datavg          concurrent
hdiskpower13    0006afbb58e1fee0                    datavg          concurrent
hdiskpower17    0006afbb58e7931e                    datavg          concurrent
hdiskpower20    0006afbb58e343af                    datavg          concurrent
hdiskpower23    0006afbb58dedc7c                    datavg          concurrent
hdiskpower26    0006afbb58e9af27                    datavg          concurrent
hdiskpower29    0006afbb58e55f6d                    datavg          concurrent
hdiskpower30    0006afbb58e11a03                    datavg          concurrent
hdiskpower31    0006afbb58ebd99c                    datavg          concurrent
hdiskpower32    0006afbb58e772e6                    datavg          concurrent
hdiskpower33    0006afbb9133c1e3                    datavg          concurrent
hdiskpower34    0006afbb9139d057                    datavg          concurrent

new disks added into the volume group, status as below
Code:
# lsvg datavg
VOLUME GROUP:       datavg                   VG IDENTIFIER:  0006afbb0000d40000000141a0c9e1da
VG STATE:           active                   PP SIZE:        128 megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      72942 (9336576 megabytes)
MAX LVs:            512                      FREE PPs:       8958 (1146624 megabytes)
LVs:                1                        USED PPs:       63984 (8189952 megabytes)
OPEN LVs:           1                        QUORUM:         10 (Enabled)
TOTAL PVs:          18                       VG DESCRIPTORS: 18
STALE PVs:          0                        STALE PPs:      0
ACTIVE PVs:         18                       AUTO ON:        no
Concurrent:         Enhanced-Capable         Auto-Concurrent: Disabled
VG Mode:            Concurrent
Node ID:            1                        Active Nodes:
MAX PPs per VG:     127000
MAX PPs per PV:     5080                     MAX PVs:        25
LTG size (Dynamic): 1024 kilobyte(s)         AUTO SYNC:      no
HOT SPARE:          no                       BB POLICY:      relocatable
PV RESTRICTION:     none

PP status
Code:
# lsvg -p datavg
datavg:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdiskpower32      active            4095        96          00..00..00..00..96
hdiskpower13      active            4095        96          00..00..00..00..96
hdiskpower31      active            4095        96          00..00..00..00..96
hdiskpower12      active            4095        96          00..00..00..00..96
hdiskpower30      active            4095        96          00..00..00..00..96
hdiskpower11      active            4095        96          00..00..00..00..96
hdiskpower29      active            4095        96          00..00..00..00..96
hdiskpower10      active            4095        96          00..00..00..00..96
hdiskpower26      active            3999        0           00..00..00..00..00
hdiskpower8       active            3999        0           00..00..00..00..00
hdiskpower23      active            3999        0           00..00..00..00..00
hdiskpower7       active            3999        0           00..00..00..00..00
hdiskpower20      active            3999        0           00..00..00..00..00
hdiskpower6       active            3999        0           00..00..00..00..00
hdiskpower17      active            3999        0           00..00..00..00..00
hdiskpower5       active            3999        0           00..00..00..00..00
hdiskpower33      active            4095        4095        819..819..819..819..819
hdiskpower34      active            4095        4095        819..819..819..819..819


Last edited by rbatte1; 11-23-2016 at 11:00 AM.. Reason: Added ICODE tags
# 2  
Old 11-23-2016
Hi danny,
try:
Code:
extendlv oravol number_of_PPs



Moderator's Comments:
Mod Comment
Please wrap all code, files, input & output/errors in CODE tags.
It makes it far easier to read and preserves multiple spaces for indenting or fixed-width data.

Last edited by rbatte1; 11-23-2016 at 11:01 AM.. Reason: Added CODE tags
# 3  
Old 11-23-2016
Quote:
Originally Posted by Bartolomeus
Hi danny,
try:
Code:
extendlv oravol number_of_PPs

Dear Bartolomeus,

Thanks for your support.

we try this before, the result as below. I don't know why is said not enough on hdiskpower6, as we checked, hdiskpower6 don't have enough space. Can we force to extend the size on the new disks? both error message on using smitty and command line.

Code:
# extendlv oravol 8176
0516-1034 lquerypv: Not enough physical partitions in physical volume hdiskpower6.
0516-788 extendlv: Unable to extend logical volume.


Last edited by rbatte1; 11-23-2016 at 11:02 AM.. Reason: Adding CODE tags into quote as I had adjusted the previous post.
# 4  
Old 11-23-2016
Quote:
Originally Posted by lckdanny

Is that related to the policy "striped" not "parallel"?
Yes!
You need enough space on all your 16 devices. lslv -l oravol will show you the affected devices.


Regards

PS
In your case the minimum extend size is 16*64K.

Code:
man extendlv
...
       Note:
       1    When extending a striped logical volume, the number of partitions must be in an even multiple of the striping width.
...


Last edited by -=XrAy=-; 11-23-2016 at 08:38 AM..
# 5  
Old 11-23-2016
Are these local disks or hardware protected in some way? (SAN provided, RAID device etc.)

The reason I ask is that you have a single copy of each PP. On real hardware you might lose the LV if any disk fails. If it is hardware protected, then you might be causing yourself an IO overhead by striping. I know it sounds counter-intuitive, but I've seen issues where spreading IO according to how the OS sees it can cause contention on the real disks when a SAN also spreads the IO. Bizarrely we improved IO when we tried to create hot-spots as the OS saw it because the SAN then really did spread the heavy IO properly.

Can you explain a little more about what hardware you have in play?


Thanks,
Robin
# 6  
Old 11-23-2016
we dont have an
Code:
lsvg -l

either to unterstand how it is organised ( mirror between to bays? etc... ) And I may be wrong as now I use only mirror pools

It looks like you are in morror and yes you added new disks but are they one in each mrirror copy etc...

If you are stripped with strict policy you are stuck...you will have to add as many disks it needs to respect the stripping policy, but one way perhaps to see if true would be to do a
Code:
 reorgvg datavg

as if the stripping is not strict, it will move blocks to unused disks and free the ones completely full, beware if this have never been done before ( running tht command...) it can take quite some time ( in hours...)
If it worked, you can try
Code:
 chfs -a size=+2000M /oradata

and see if that works.. if so you are a happy guy...
# 7  
Old 11-23-2016
I don't think that there are mirrors in play for this LV. On the lslv oravol we have LPs matching PPs and COPIES value of 1.

This could well be SAN provided, especially if it is Oracle RAC in play as suggested by these lines from the lsvg
Code:
:
Concurrent:         Enhanced-Capable         Auto-Concurrent: Disabled
VG Mode:            Concurrent
:

I'm not sure if reorgvg will work in Enhanced-Capable or not. It might well be worth stopping all but one node of the cluster (assuming it is clustered)


Robin
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

No space in volume group. How to create a file system using existing logical volume

Hello Guys, I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var. I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies

2. AIX

Position of the logical volume on the physical volume

Hello everyone, I just read that while creating a logical volume(LV) we can choose the region of the physical volume (PV) in which the LV should be created. When I say region I mean: outer edge - outer middle - center - inner middle and inner edge. Can anyone help me understand the utility... (11 Replies)
Discussion started by: adilyos
11 Replies

3. HP-UX

[Solved] How to extend a mirrored logical volume?

Want to extend the /home filesystem: Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol4 262144 260088 2056 99% /home root@server:./root # vgdisplay vg00 --- Volume groups --- VG Name /dev/vg00 VG Write Access read/write VG Status available Max LV 255 Cur LV 11 Open... (4 Replies)
Discussion started by: proactiveaditya
4 Replies

4. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

Hi, I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies 1)Physical Volume 2)Volume Group 3)Logical Volume 4)Physical Partition Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies

5. HP-UX

Unable To Extend the Size of a Logical Volume File System

Background: # uname -a HP-UX deedee B.11.23 U ia64 4294967295 unlimited-user license deedee.rsn.hp.com:/ # bdf /opt Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol6 6553600 6394216 158144 98% /opt /opt is almost full... (3 Replies)
Discussion started by: Rob Sandifer
3 Replies

6. AIX

Logical volume name conflict in two volume group

Hello, I am a french computer technician, and i speak English just a little. On Aix 5.3, I encounter a name conflict logical volume on two volume group. The first volume lvnode01 is OK in rootvg and mounted. It is also consistent in the ODM root # lsvg -l rootvg |grep lvnode01 ... (10 Replies)
Discussion started by: dantares
10 Replies

7. AIX

Basic Filesystem / Physical Volume / Logical Volume Check

Hi! Can anyone help me on how I can do a basic check on the Unix filesystems / physical volumes and logical volumes? What items should I check, like where do I look at in smit? Or are there commands that I should execute? I need to do this as I was informed by IBM that there seems to be... (1 Reply)
Discussion started by: chipahoys
1 Replies

8. AIX

Help - can't extend logical volume ?

Hi, Smit "Increase the Size of a Logical Volume" command failed. Output: ---------------------------------------------------------- Command: failed stdout: yes stderr: no Before command completion, additional instructions may appear below. The distribution of this command (111) failed on... (2 Replies)
Discussion started by: vilius
2 Replies

9. UNIX for Advanced & Expert Users

LVM - Extending Logical Volume within Volume Group

Hello, I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB. If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information Regards Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies

10. AIX

Extend one Logical Volume

Hi All, I am new to AIX. I need to extend one Logical Volume it is jfs type on On AIX 5.1. I have enough free space on the volume group for this extension Can I use smitty chjfs , will this do it without interruptions to the application that is using this Logical Volume. Thanks Scampi (1 Reply)
Discussion started by: scampi
1 Replies
Login or Register to Ask a Question