topic Re: Not enough extent in Operating System - HP-UX

Not enough extent

Lee Bryant — Wed, 22 Oct 2003 07:13:02 GMT

Can I add extent to this filesystem while it is mounted? I see that I am out of PE on all but one disk, is that why this command is not working and how do I fix it? Plus, can it be done on-line or while mounted? I am getting this error when running this command: lvextend -L 400 /dev/vg00/lvol5
lvextend: Not enough free physical extents available.
Logical volume "/dev/vg00/lvol5" could not be extended.
Failure possibly caused by strict allocation policy

Also, can the policy be change while a f/s is mounted?

Thanks very much!!!
--- Physical volumes ---
PV Name /dev/dsk/c4t6d0
PV Status available
Total PE 2169
Free PE 0
Autoswitch On

PV Name /dev/dsk/c3t6d0
PV Status available
Total PE 2169
Free PE 0
Autoswitch On

PV Name /dev/dsk/c4t5d0
PV Status available
Total PE 2169
Free PE 0
Autoswitch On

PV Name /dev/dsk/c3t5d0
PV Status available
Total PE 2169
Free PE 0
Autoswitch On

PV Name /dev/dsk/c9t0d5
PV Status available
Total PE 2157
Free PE 1044
Autoswitch On

Re: Not enough extent

Steven E. Protter — Wed, 22 Oct 2003 07:21:33 GMT

Strict allocation warnings mean the volume group cant be non-contiguous.

You should be able to change the policy while its mounted. lvchange is the command.

SEP

Re: Not enough extent

Rita C Workman — Wed, 22 Oct 2003 07:31:51 GMT

If you have OnlineJFS you can extend without taking anything down, check to see if this shows as installed Product number is B3929 I think:
swlist | grep -i online

If you have this...then do a simple extend and do not state the c-t-d- in your command line, let the system grab it...:

lvextend -l xxx /dev/vgname/lvolx

Then extend your filesystem:

fsadm -F vxfs -b m /filesystem

Note I put an 'm' right after the new size to denote it's in Mb.

Hope this helps,
Rita

...If you don't have Online JFS then you will have to take filesystem down (possibly reboot and go into single user) and do it with lvextend & extendfs commands.

Re: Not enough extent

john korterman — Wed, 22 Oct 2003 07:43:48 GMT

Hi,
an error concerning "strict allocation policy" can also mean that as you have only free space on one physical disk, an extension cannot be mirrored on a different disk, which would make it a high-risk venture; hence extension not allowed.
Even if possible, I would not recommend changing the allocation policy as you would be in deep trouble even if only a single disk crashes!

regards,
John K.

Re: Not enough extent

Lee Bryant — Wed, 22 Oct 2003 08:17:38 GMT

Thank you for the responses/answers thus far. I will lokk into them. I look forward to additional help and suggestions!
Particluarly, can and how do I add more PEs to the other disk?

Thanks!

Re: Not enough extent

Pete Randall — Wed, 22 Oct 2003 08:23:59 GMT

Lee,

You can't add PE(s) to the other disk - it's full. The only way to make more Physical Extents available on it would be to move one of you logical volumes from the "full" disk to the "less full" disk.

I would be interested in seeing exactly what we're dealing with here. Could you please post the output of "lvdisplay /dev/vg00/lvol5" and "bdf -l". Thanks.

Pete

Re: Not enough extent

Lee Bryant — Wed, 22 Oct 2003 16:26:32 GMT

Pete, thanks and here you go. I hope this helps!

# lvdisplay /dev/vg00/lvol5
--- Logical volumes ---
LV Name /dev/vg00/lvol5
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 124
Current LE 31
Allocated PE 62
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

# bdf -l
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 143360 70977 67904 51% /
/dev/vg00/lvol1 83733 47018 28341 62% /stand
/dev/vg00/lv_vertel
1536000 886232 609189 59% /vertel
/dev/vg00/lvol7 745472 674840 67118 91% /var
/dev/vg00/lv_save 2097152 1794948 283379 86% /var/adm/sw/save
/dev/vg00/lvol6 880640 626266 238480 72% /usr
/dev/vg00/lvol5 126976 126976 0 100% /tmp
/dev/vg00/lvol4 655360 621099 32182 95% /opt
/dev/vg00/lv_registry
53248 17734 33337 35% /opt/registry
/dev/vg00/lv_patrol
512000 484052 26419 95% /opt/patrol
/dev/vg00/lv_oracle8
2048000 736818 1229357 37% /opt/oracle8/CTMS
/dev/vg00/lv_extif 614400 501326 106054 83% /opt/extif
/dev/vg00/lv_clarify
1536000 1215490 300509 80% /opt/clarify
/dev/vg00/lvol8 20480 7378 12356 37% /home
/dev/vg00/lv_weblogic
2048000 657237 1306759 33% /home/weblogic
/dev/vg_oracle/lv_ora8i
3145728 2276911 814524 74% /opt/oracle8i
/dev/vg_app/lv_rule
53248 1404 48664 3% /opt/clarify/bs_rule
/dev/vg_app/lv_scripts
524288 10198 482020 2% /opt/clarify/devl/scripts
/dev/vg_app/lv_archive
3096576 1987109 1040207 66% /opt/clarify/devl/export/archive
/dev/vg_app/lv_msgstore
102400 1185 94893 1% /opt/extif/top/mediator/BTB/msgStore
/dev/vg_app/lv_conf
155648 1313 144741 1% /home/OTMP/conf
/dev/vg_app/lv_xref
53248 1141 48854 2% /opt/extif/top/mediator/BTB/XRefFiles
/dev/vg_app/lv_omnibus
307200 59004 232702 20% /opt/Omnibus
/dev/vg_app/lv_web_app
102400 13993 82905 14% /home/weblogic/weblogic60/wlserver6.0/config/bmpDomain/applications

# find /tmp -exec ls -ld {} \;
drwxrwxrwx 6 bin bin 18432 Oct 22 21:35 /tmp
drwxrwxrwx 2 root sys 96 Oct 21 21:44 /tmp/lost+found
drwx------ 2 root root 96 Sep 13 17:28 /tmp/.AgentSockets
srwx------ 1 root root 0 Sep 13 17:28 /tmp/.AgentSockets/A
-rw-rw-rw- 1 extif ctms 0 Oct 22 21:31 /tmp/ctmsif_monitor.out
-rw-rw-rw- 1 root root 0 Oct 22 21:31 /tmp/truncmon.out
-rw-rw-rw- 1 root root 15 Oct 22 21:32 /tmp/trunccroncln.out
drwxrwxrwx 2 ora8ctms dba 96 Oct 21 17:21 /tmp/.oracle
drwxrwxrwx 2 patrol dba 96 Oct 21 21:43 /tmp/patrol

Re: Not enough extent

Todd McDaniel_1 — Thu, 23 Oct 2003 10:03:34 GMT

Lee,

A few things.. bad news im afraid.

First your command to add extents to a LV will fail how you have it listed b/c the associated disks with that LVOL have no extents left... of course I am assuming that /dev/dsk/c9t0d5 is not in LVOL5. if it were your command would not have failed. ALSO, it will fail again b/c you have no extents avail on a 2nd disk for the mirroring.

With a mirrored filesystem, you must add an equal number of extents to both the primary and mirror... Since you have strict allocation, the mirror extents cant be from the same disk as the primary which is a good thing... that would be a very bad thing...

I dont see that you can do what you are intending with the current setup...

You need to do a few things. First add 2 new disks to your VG that are identical size. then extend the Lvol you intend.

with your current VG with 5 disks, you cant extend the LVOL. YOU COULD do it if you had another disk with 1044 extents avail as you do with /dev/dsk/c9t0d5 but since you dont, it will not be possible.