Sponsored Content
Full Discussion: Free PP Allocation problem
Operating Systems AIX Free PP Allocation problem Post 302505775 by kah00na on Thursday 17th of March 2011 05:26:23 PM
Old 03-17-2011
PPs (physical partitions) represent free space on each disk. Each PP is 256 MB in your rootvg. You can see that in the "lsvg rootvg" output:
Code:
PP SIZE:        256 megabyte(s)

1 PP is the same as 256 MB of free space. The only way to get more free PPs is to move stuff off the disk to the other disk. LPs represent how may logical partitions of your rootvg are being used. If the disk is not mirrored, then a LP is the same as a PP. If your disk is mirrored, then LPs will be half the number of your PPs unless the logical volume is not mirrored like your /var/vio/VMLibrary. Since your "/var/vio/VMLibrary" is only on hdisk1, shrinking that filesystem size will only free PPs on hdisk1. There is no way to move free PPs from one disk to another. You can move logical volumes between your disks (migratepv -l) to free up PPs on one disk but you can't move free space from one disk over to another.

If your goal is to increase /usr by 2.5 GB, you should have the space according to your "lsvg rootvg" output:
Code:
$ lsvg rootvg
VOLUME GROUP:       rootvg                   VG IDENTIFIER:  0007f6fa0000d4000000012667f326b5
VG STATE:           active                   PP SIZE:        256 megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      1092 (279552 megabytes)
MAX LVs:            256                      FREE PPs:       301 (77056 megabytes)
LVs:                16                       USED PPs:       791 (202496 megabytes)
OPEN LVs:           14                       QUORUM:         1 (Disabled)
TOTAL PVs:          2                        VG DESCRIPTORS: 3
STALE PVs:          0                        STALE PPs:      0
ACTIVE PVs:         2                        AUTO ON:        yes
MAX PPs per VG:     32512
MAX PPs per PV:     1016                     MAX PVs:        32
LTG size (Dynamic): 1024 kilobyte(s)         AUTO SYNC:      no
HOT SPARE:          no                       BB POLICY:      relocatable

Run this after logging in as padmin:
Code:
oem_setup_env
chfs -a size=+2560MB /usr

 

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] [--noudevsync] [-i|--stripes Stripes [-I|--stripesize StripeSize]] {-l|--extents [+]LogicalExtentsNumber[%{VG|LV|PVS|FREE|ORIGIN}] | -L|--size [+]LogicalVolumeSize[bBsSkKmMgGtTpPeE]} [-f|--force] [-n|--nofsck] [-r|--resizefs] [-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 for common options. --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. -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 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. -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) -f, --force Proceed with size extension without prompting. -n, --nofsck Do not perform fsck before extending filesystem when filesystem requires it. You may need to use --force to proceed with this option. -r, --resizefs Resize underlying filesystem together with the logical volume using fsadm(8). Examples "lvextend -L +54 /dev/vg01/lvol10 /dev/sdk3" tries to extend the size of that logical volume by 54MB 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 /dev/vg01/lvol01 /dev/sdk3" tries to extend the size of that logical volume by the amount of free space on physical volume /dev/sdk3. This is equivalent to specifying "-l +100%PVS" on the command line. "lvextend -L+16M vg01/lvol01 /dev/sda:8-9 /dev/sdb:8-9" tries to extend a logical volume "vg01/lvol01" by 16MB using physical extents /dev/sda:8-9 and /dev/sdb:8-9 for allocation of extents. SEE ALSO
fsadm(8), lvm(8), lvcreate(8), lvconvert(8), lvreduce(8), lvresize(8), lvchange(8) Sistina Software UK LVM TOOLS 2.02.95(2) (2012-03-06) LVEXTEND(8)
All times are GMT -4. The time now is 08:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy