Sponsored Content
Full Discussion: Help growing fs
Operating Systems AIX Help growing fs Post 302969446 by bbbngowc on Tuesday 22nd of March 2016 11:25:44 PM
Old 03-23-2016
Huh? Am I misreading that number? That's not 1TB of available storage?

I'm looking at the free PPs in the output.

---------- Post updated at 11:25 PM ---------- Previous update was at 10:44 PM ----------

Ok, I figured this out. The volume group has 2 PVs. When I expanded the disk, only 1 PV was expanded. I expanded the second disk and then rescanned the vg using chvg -g myvg.

Now I'm able to grow the fs no problems.

Thanks for chiming in fellas. Much appreciated.
 

10 More Discussions You Might Find Interesting

1. AIX

AIX Growing Files

Hi Everybody, I want to know the names & locations of the common AIX files which it's size keep growing. I think there is a procedure to clean these files to avoid the space overflow, I wish also if anybody can tell me what is the proper procedure to make more available space. Another issue, that... (2 Replies)
Discussion started by: aldowsary
2 Replies

2. UNIX for Dummies Questions & Answers

.osm file growing

my /etc/.osm file is growing rapidly and logging large amounts of activity. Can anyone tell me what this file is for and what types of information is logged in this file. Thanks in advance for your help!! (1 Reply)
Discussion started by: golfs4us
1 Replies

3. AIX

Help growing iscsi lun

Hi, I have an iSCSI LUN of 200GB. I increased it to 250GB and when I try to increase the size of the vg, I'm getting an error that none of the volumes have increased in size. How can I get the OS to see the additional 50GB? ---------- Post updated at 03:22 PM ---------- Previous update... (9 Replies)
Discussion started by: bbbngowc
9 Replies

4. Solaris

Growing a file system-SVM

Hi gurus Im a newbie in solaris..I need to extend file system space in solaris 10 which is using SVM..I have a file system /pin02 which is 93% full n needs to be extended..only 3.6 gb avail space left..the file system is not mirrored...normal ufs file system only..can u please tel me t... (6 Replies)
Discussion started by: madanmeer
6 Replies

5. Solaris

Growing /opt

Hi, /opt on my disk is almost 90%. I thought of growing it. I followed the below procedure: 1. added a new hard disk 2. formatted the same with ufs 3. created a slice and tried to label it as "opt" with "wm" permissions. but got stuck at 3 as it is not allowing me to label the slice... (9 Replies)
Discussion started by: EmbedUX
9 Replies

6. Filesystems, Disks and Memory

Growing a FS over 1T - can it be done ?

Greeting Forumers! I've been asked to increase space in a FS that is currently 740G in size: Filesystem size used avail capacity Mounted on /dev/md/dsk/d664 740G 424G 308G 58% /ora_back My SAN administrator has allocated 5 LUNs of 200G each - this will make... (3 Replies)
Discussion started by: bluescreen
3 Replies

7. Solaris

Help with Growing FS

Ok so I just installed Solaris 10 on my x86 laptop. But I too the defaults and now all of the FS's are very small. I can't install anything. The drive is a 40GB but only about 11GB is being seen and used. How can I get the OS to see and use the rest of the drive? I was just going to reinstall, but... (3 Replies)
Discussion started by: bbbngowc
3 Replies

8. Shell Programming and Scripting

growing files

I am trying to be pro-active and prevent FS from filling up. I know about the df/du command also find -size -mtime ....... What I want to know is there a way I can do a find to see which files have been accessed or modified after a specifc YYYYMMDD-HHMMSS. What I am really looking for is to... (4 Replies)
Discussion started by: BeefStu
4 Replies

9. Red Hat

Growing filesystem using LVM

Hi, I have a LUN presented to a Linux system and would like to ask if someone can advise if the logical volume /dev/mapper/VGOra-LVOra 12G 11G 659M 95% /usr/app/oracle can be extended. Is there any free space to allocate.... The LUN (25G) has been configured as follows: LUN - ROOT...... (4 Replies)
Discussion started by: jamba1
4 Replies

10. AIX

/usr is growing fast

I'm having a strange Phenomenon here in one of my servers /usr file system is growing fast and it went wild. I have searched the entire file system for large , growing and newly created files with no clue what's going on I have found nothing strange. Any further idea a snapshot from df's ... (4 Replies)
Discussion started by: h@foorsa.biz
4 Replies
vgreduce(1M)															      vgreduce(1M)

NAME
vgreduce - remove physical volumes from an LVM volume group SYNOPSIS
autobackup] vg_name pv_path ... autobackup] vg_name pv_path autobackup] vg_name DESCRIPTION
The command removes each physical volume specified by a pv_path argument from volume group vg_name. The command with option removes all missing physical volumes from the volume group. All but one physical volume can be removed. The last physical volume must remain in the volume group so that the logical volume driver can continue to operate. The last physical volume in the volume group can be removed with the command (see vgremove(1M)). Before executing remove all logical volumes residing on each physical volume represented by a pv_path by executing the command (see lvre- move(1M)). Any physical volume in the pv_path list that is also a member of a physical volume group (as defined in is also removed from the physical volume group. If the physical volume happens to be the last one in the physical volume group, the physical volume group is also removed from the volume group. When a physical volume in the pv_path list has multiple the physical volume is not removed from the volume group until all the links to the volume are removed. When a physical volume in the pv_path list is the (in use) to a physical volume, removing the link forces LVM to switch to the (For information on alternate links, see lvm(7)). When the pv_path removed is an to the device, only the link is removed; the volume group and physical volume are otherwise unchanged. When a physical volume is added into volume groups version 2.0 or higher, the number of physical extents available on this device will be added into of the volume group (see vgdisplay(1M)). If the size of physical volume is such that would exceed the VG Max Extents of the volume group, the number of physical extents available on this device will be reduced accordingly (see vgextend(1M)). If a subsequent on a different physical volume, frees up space, then the number of extents allocated to the partial physical volume is automatically increased. Under these circumstances the command will display the old and the new values for the count for this partial physical volume (see pvdis- play(1M)). Options and Arguments recognizes the following options and arguments: 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 volume group. This is the default. After this command executes, the command (see vgcfgbackup(1M)) is executed for the volume group. Do not back up configuration changes this time. Force the reduction of missing physical volumes from the specified volume group. obtains the name of each physical volume (PV) belonging to the volume group. It then reads the kernel PV structures to work out which PVs are missing. PVs which are missing will be candidates for removal. If all the physical extents on the missing PV are free then it will be removed from the volume group. Otherwise will report the physical to logical extent mapping. For missing PVs which have extents in use, you must free up all the extents by using the or commands (see lvreduce(1M) and lvremove(1M)) and re-run with the option. This option is most commonly used when the command (see vgdisplay(1M)) shows "Cur PV" higher than "Act PV" and all of the PVs belonging to the volume group are attached. This option only works on PVs and not on links. See the option for details on handling missing links. Removes the specified pv_path/s from the or file. This task will only be performed if the pv_path is currently marked as missing from the volume group. This option was mainly designed for the problem where the or the command place too many links beyond the max limit allowed in the or file. Currently the max limit is 8 paths to a PV (seven alternates and one primary). In this situation, invoking the command without the option will not resolve the condition because the path is not attached to the volume group. Similarly, this condition can not be overcome by invoking with the option, as the same works on physical volumes rather than the links. pv_path The block device path name of a physical volume. vg_name The path name of the volume group. 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). In the case a PV alternate link is reduced, is updated only on the server node. In the case a PV is reduced, all the PV device special files are removed from on all the nodes sharing the volume group. When a node wants to share the volume group, the user must first execute a if physical volumes were removed at the time the volume group was not activated on that node. 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
Remove physical volume from volume group Force, reduction of missing PVs from volume group: The following messages will appear after missing PVs has been removed successfully: PV with key 0 successfully deleted from vg Repair done, please do the following steps.....: 1. Save or to another file. 2. Remove or 3. Use to recreate or 4. NOW use to save the LVM setup. Remove the physical volume from the volume group when the physical volume is still in the or file but is currently marked as missing from the volume group: SEE ALSO
lvmpud(1M), vgchange(1M), vgcreate(1M), vgdisplay(1M), vgextend(1M), intro(7), lvm(7). vgreduce(1M)
All times are GMT -4. The time now is 01:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy