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(1M)															      lvextend(1M)

NAME
lvextend - increase space, increase mirrors for LVM logical volume SYNOPSIS
autobackup] le_number | lv_size | mirror_copies lv_path [pv_path ... | pvg_name ...] Remarks Mirrored disk operations require the installation of the optional HP MirrorDisk/UX software, which is not included in the standard HP-UX operating system. DESCRIPTION
The command can increase a logical volume's allocated extents, or increase its number of mirrored copies. Other logical volume characteristics can be modified with the and commands (see lvchange(1M) and lvreduce(1M)). To limit the allocation to specific physical volumes, specify the physical volume names as pv_path arguments or specify the physical volume group names as pvg_name arguments. Otherwise, all of the physical volumes in a volume group are available for allocating new physical extents. LVM always ensures that physical extent allocation can satisfy the current allocation policy or policies. If a physical volume is not suitable for use with a certain allocation policy, it is not used during physical extent allocation, even it is specified in a pv_path argument or indirectly in a pvg_name argument. The pvg_name argument is allowed only if one of the allocation policies of the logical volume is PVG-strict. Options and Arguments The option is only meaningful if the optional HP MirrorDisk/UX software has been installed. recognizes the following options and arguments: lv_path The block device path name of a logical volume. pv_path The block device path name of a physical volume. pvg_name The name of a physical volume group (see lvmpvg(4)). Set automatic backup for this invocation of this command. autobackup can have one of the following values: Automatically back up configuration changes made to the logical volume. This is the default. After this command executes, the command (see vgcfgbackup(1M)) is executed for the volume group to which the logical volume belongs. Do not back up configuration changes this time. Increase the space allocated to the logical volume, specified in logical extents. le_number is a decimal value greater than the current number of logical extents. le_number must be at least 1 and no greater than a volume group version-dependent maximum; use the command to determine the maximum number of logical extents for the volume group version. One, and only one, or option must be supplied. Increase the space allocated to the logical volume, specified in megabytes. lv_size is a decimal value greater than the current logical volume size. lv_size must be at least 1 and no greater than a volume group version-dependent maximum; use the command to determine the maximum logical volume size for the volume group version. lv_size is rounded up to the nearest multiple of the logical extent size, equivalent to the physical extent size defined for the volume group by the command (see vgcreate(1M)). One, and only one, or option must be specified. Set the number of mirror copies allocated for each logical extent. A mirror copy contains the same data as the original. mirror_copies must be at least 1 and no greater than a volume group version-dependent maximum; use the command to determine the maximum number of mirror copies for the volume group version. mirror_copies must be greater than the current value. Data in the new copies is synchronized unless the option is specified. The synchronization process can be time consuming, depending on hardware characteristics and the amount of data. One, and only one, or option must be specified. Do not synchronize the new mirror copies. This may affect data high availability so use or to synchronize the mirrors. The option must be specified along with this option. Striped Logical Volume considerations Striped and mirrored logical volumes are supported. An increase in size of a striped logical volume is done by increments of stripes logical extents. One increment corresponds to stripes physical extents if the volume is not mirrored or to stripes * (mirror_copies + 1) physical extents if the volume is mirrored. stripes is the number of disks the logical volume is striped across. It is set with the option stripes of the command. mirror_copies is the number of mirror copies allocated for each extent. It is set with the option of the and commands. LVM striped logical volumes are always allocated using the strict or PVG-strict allocation policies. Each physical extent of an increment is allocated on a different physical volume in the volume group. A size increase of a striped volume requires at least stripes (or stripes * (mirror_copies + 1) if the volume is mirrored) physical volumes with adequate free space and meeting the allocation policy. An increase of the number of mirror copies of a striped volume requires at least (stripes times the number of copies to add) physical vol- umes with adequate free space and meeting the allocation policy. Shared Volume Group Considerations For volume group version 1.0 and 2.0, cannot be used if the volume group is activated in shared mode. For volume groups version 2.1 (or higher), can be performed when activated in either shared, exclusive, or standalone mode. Note that the daemon must be running on all the nodes sharing a volume group activated in shared mode. See lvmpud(1M). If physical volume groups are passed as arguments, uses the physical volume group file of the system where the command is issued (the server). LVM shared mode is currently only available in Serviceguard clusters. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Increase the number of the logical extents of a logical volume to 100: Increase the logical volume size to 400 MB: Allocate two mirrors (that is, two copies of the original) for each logical extent of a logical volume: Mirror a logical volume onto a particular physical volume. Allocate one mirror and do not synchronize the new mirror copy: Increase the size of a file system existing on a logical volume. First, increase the size of the logical volume. Unmount the file system. Extend the file system to occupy the entire (larger) logical volume. Remount the file system. WARNINGS
The creation of striped and mirrored logical volume(s) may prevent the import and activation of the volume group on an earlier HP-UX release. See lvcreate(1M) on the earlier release to see if it explicitly states that striping and mirroring is supported. If the striped and mirrored logical volumes of the volume group are removed or un-mirrored, the volume group becomes again compatible with the older HP-UX releases. SEE ALSO
lvchange(1M), lvcreate(1M), lvdisplay(1M), lvmadm(1M), lvmpud(1M), lvreduce(1M), lvsync(1M), pvchange(1M), pvdisplay(1M), vgsync(1M), intro(7), lvm(7). lvextend(1M)
All times are GMT -4. The time now is 07:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy