Sponsored Content
Full Discussion: Free PP Allocation problem
Operating Systems AIX Free PP Allocation problem Post 302505004 by broonster on Wednesday 16th of March 2011 12:42:20 AM
Old 03-16-2011
Free PP Allocation problem

Firstly, I can't stress enough how much of a newb I am to AIX or Linux in general so please be very patient. I am strictly a MS man, however I now need to administer an IBM power series blade server which sits on top of an AIX VIOS. The VIOS version I am running is 2.1.2.0 and it is mirrored on two physical disks.

I am currently trying to install the latest version of the VIOS but when I attempt to run the command updateios it complains that there is not enough space in the /usr filesystem.

I then attempted to extend the /usr filesytem using extendlv but I get the error "0516-404 allocp: This system cannot fulfill the allocation request.There are not enough free partitions or not enough physical volumes to keep strictness and satisfy allocation requests. The command should be retried with different allocation characteristics."

In troubleshooting this error on google I think the problem lies in the allocation of my free PPs over the two mirrored disks. Here is the output of lsvg -pv rootvg.

Code:
$ lsvg -pv rootvg
rootvg:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdisk0            active            546         0           00..00..00..00..00
hdisk1            active            546         301         83..00..00..109..109

I think what I need to do is move some of the 301 free PPs from hdisk1 over to hdisk0 but I haven't a clue where to even start. Can anyone help? Again, go easy I'm extremely new to this and barely know the connection between LVs, PVs, PPs and LPs.

Moderator's Comments:
Mod Comment Please use [code] and [/code] tags when posting code, data or logs etc. to preserve formatting and enhance readability, thanks.

Last edited by zaxxon; 03-16-2011 at 04:36 AM.. Reason: code tags
 

7 More Discussions You Might Find Interesting

1. SCO

Terminal Allocation Problem

Hello All, I am facing a problem on SCO Open Server V 5x, We are using serial communication on dumb terminals, right now i am facing a problem on some terminals, as they are not showing thier previous tty no, as tty13 or tty18, but they are showing ttya6 or ttya4, i also tried to move and link... (5 Replies)
Discussion started by: Awadhesh
5 Replies

2. Programming

Memory allocation problem

I have a program that will fetch some particular lines and store it in a buffer for further operations.The code which is given below works but with some errors.I couldn't trace out the error.Can anybody help on this plz?? #include <stdio.h> #include <stdlib.h> #include<string.h> #define... (1 Reply)
Discussion started by: vigneshinbox
1 Replies

3. Programming

Is there a problem with the memory allocation???

I have a scenario like the client has to search for the active server.There will be many servers.But not all server are active.And at a time not more than one server will be active. The client will be in active state always i.e, it should always search for an active server until it gets one.I... (1 Reply)
Discussion started by: vigneshinbox
1 Replies

4. Programming

dynamic allocation vs static allocation in c

i wrote a tiny version of tail command using a large buffer statically allocated but, in a second time, i found another version in which i use a bidimensional array dynamically allocated. here is the first version /*my tiny tail, it prints the last 5 line of a file */ #include<stdio.h>... (4 Replies)
Discussion started by: lucasclaus
4 Replies

5. Solaris

MountPoint / is 8% with 899.49MB free crossing threshold of 10% free

Hi, I have a problem one of the server file system cross the limitation MountPoint / is 8% with 899.49MB free crossing threshold of 10% free out put please help how to resolve this dev/vx/dsk/bootdg/rootvol 9.8G 8.8G 956M 91% / /devices ... (3 Replies)
Discussion started by: sriniva0
3 Replies

6. Solaris

Block-based allocation and Extent-based allocation in Solaris

Hi guys! Could you tell me what's this figure about? (See the attached figure below.) This is a representation of block allocation filesystem and extent allocation filesystem in Solaris. Does this mean that in a block-based allocation, data are placed in individual blocks while in... (0 Replies)
Discussion started by: arah
0 Replies

7. UNIX for Dummies Questions & Answers

Memory allocation problem

I am using ubuntu. I have written a program to calculate prime factors. it works perfectly fine till entered number is less than 9989 (or so ) but when one enters a number higher than that, for example 15000, it does not work. Can anyone guide me whats the problem ? although new codes are welcome,... (2 Replies)
Discussion started by: Abhishek_kumar
2 Replies
LVEXTEND(8)						      System Manager's Manual						       LVEXTEND(8)

NAME
lvextend - extend the size of a logical volume SYNOPSIS
lvextend [--alloc AllocationPolicy] [-A|--autobackup {y|n}] [-d|--debug] [-h|-?|--help] [-f|--force] [-i|--stripes Stripes [-I|--stripesize StripeSize]] {-l|--extents [+]LogicalExtentsNumber[%{VG|LV|PVS|FREE|ORIGIN}] | -L|--size [+]LogicalVolumeSize[bBsSkKmMgGtTpPeE]} [-n|--nof- sck] [--noudevsync] [-r|--resizefs] [--use-policies] [-t|--test] [-v|--verbose] LogicalVolumePath [PhysicalVolumePath[:PE[-PE]]...] DESCRIPTION
lvextend allows you to extend the size of a logical volume. Extension of snapshot logical volumes (see lvcreate(8) for information to cre- ate snapshots) is supported as well. But to change the number of copies in a mirrored logical volume use lvconvert(8). OPTIONS
See lvm(8) for common options. -f, --force Proceed with size extension without prompting. -l, --extents [+]LogicalExtentsNumber[%{VG|LV|PVS|FREE|ORIGIN}] Extend or set the logical volume size in units of logical extents. With the '+' sign the value is added to the actual size of the logical volume and without it, the value is taken as an absolute one. The total number of physical extents allocated will be greater than this, for example, if the volume is mirrored. The number can also be expressed as a percentage of the total space in the Volume Group with the suffix %VG, relative to the existing size of the Logical Volume with the suffix %LV, of the remaining free space for the specified PhysicalVolume(s) with the suffix %PVS, as a percentage of the remaining free space in the Volume Group with the suffix %FREE, or (for a snapshot) as a percentage of the total space in the Origin Logical Volume with the suffix %ORIGIN. The resulting value is rounded upward. N.B. In a future release, when expressed as a percentage with PVS, VG or FREE, the number will be treated as an approximate upper limit for the total number of physical extents to be allocated (including extents used by any mirrors, for example). The code may currently allocate more space than you might otherwise expect. -L, --size [+]LogicalVolumeSize[bBsSkKmMgGtTpPeE] Extend or set the logical volume size in units of megabytes. A size suffix of M for megabytes, G for gigabytes, T for terabytes, P for petabytes or E for exabytes is optional. With the + sign the value is added to the actual size of the logical volume and with- out it, the value is taken as an absolute one. -i, --stripes Stripes Gives the number of stripes for the extension. Not applicable to LVs using the original metadata LVM format, which must use a sin- gle value throughout. -I, --stripesize StripeSize Gives the number of kilobytes for the granularity of the stripes. Not applicable to LVs using the original metadata LVM format, which must use a single value throughout. StripeSize must be 2^n (n = 2 to 9) -n, --nofsck Do not perform fsck before extending filesystem when filesystem requires it. You may need to use --force to proceed with this option. --noudevsync Disable udev synchronisation. The process will not wait for notification from udev. It will continue irrespective of any possible udev processing in the background. You should only use this if udev is not running or has rules that ignore the devices LVM2 cre- ates. -r, --resizefs Resize underlying filesystem together with the logical volume using fsadm(8). --use-policies Resizes the logical volume according to configured policy. See lvm.conf(5) for some details. Examples Extends the size of the logical volume "vg01/lvol10" by 54MiB on physical volume /dev/sdk3. This is only possible if /dev/sdk3 is a member of volume group vg01 and there are enough free physical extents in it: lvextend -L +54 /dev/vg01/lvol10 /dev/sdk3 Extends the size of logical volume "vg01/lvol01" by the amount of free space on physical volume /dev/sdk3. This is equivalent to specifying "-l +100%PVS" on the command line: lvextend /dev/vg01/lvol01 /dev/sdk3 Extends a logical volume "vg01/lvol01" by 16MiB using physical extents /dev/sda:8-9 and /dev/sdb:8-9 for allocation of extents: lvextend -L+16M vg01/lvol01 /dev/sda:8-9 /dev/sdb:8-9 SEE ALSO
fsadm(8), lvm(8), lvm.conf(5), lvcreate(8), lvconvert(8), lvreduce(8), lvresize(8), lvchange(8) Sistina Software UK LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26) LVEXTEND(8)
All times are GMT -4. The time now is 09:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy