Sponsored Content
Operating Systems AIX Increasing ./usr or any filesystem Post 302453631 by frank_rizzo on Thursday 16th of September 2010 12:56:29 AM
Old 09-16-2010
Quote:
Originally Posted by pilotHans
seems that everythings fine. It did add 3G i guess.hmm..Now lets hope all the original files in /usr are there Smilie

+ One additional question.

Can I keep on adding the size? meaning lets say after this I still find 3G not enough and I want to add more, would it effect anything? My assumption is No.
chfs works fine and does not affect existing data. you can keep adding space as long as you have physical space available. I would strongly suggest moving non-OS data out of /usr though. This will make backup/restores go much smoother and avoid having an application affect the OS in a negative way.

chfs is normally the only command that is needed for this. be *very* careful with LVM commands. They are very powerful and can make for a bad day if used improperly.

Last edited by frank_rizzo; 09-16-2010 at 01:59 AM.. Reason: add comment
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Increasing filesystem space

Now, i know a ufs file system can be increased using mkfs but hwo do I take space from a file system and add it to another file system? at my job here, that seems to be possible because I see request on it almost every day. what is the exact command to do this and does the system need to be... (1 Reply)
Discussion started by: TRUEST
1 Replies

2. AIX

Increasing the FileSystem Size

Hi Everybody, I have AIX 4.3 and I have a FileSystem with 400GB size, which called /db/run. Because of grow up of the application's data, more storage has been added 200GB. To add this space without affecting the application & the application's requirements, I have to add this 200GB to the existed... (9 Replies)
Discussion started by: aldowsary
9 Replies

3. Filesystems, Disks and Memory

how can I extend /usr filesystem

How can extend /usr filesystem in hp-ux 11.11 (I'm not using online JFS) ? (0 Replies)
Discussion started by: pedro_lezaeta
0 Replies

4. Solaris

Mount /usr as a separate filesystem

Hi All, I have mount /usr directory as a seperate filesystem.The /usr directory includedd in / root file system.I have to mount it as seperate. Please Help me, Thanks and Regards, (7 Replies)
Discussion started by: lbreddy
7 Replies

5. AIX

/usr/nsr needing cleanup (filesystem 100%)

Hi, got a nice surprise this morning. I have an alert saying I have a server with the filesystem /usr/nsr full at 100%. Upon looking at its content I have no idea what to clean up. The only files that were created within the past few days are kind of small. So I suspect it was always almost... (3 Replies)
Discussion started by: Browser_ice
3 Replies

6. Solaris

smf fails to mount svc:/system/filesystem/usr:default

http://i44.tinypic.com/2cmq7vn.jpg Please help me on this issue i'm using solaris on vmware x86 even i runed fsck on root disk like 'fsck -Y /dev/rdsk/c0d0s0 ' but again after reboot it is going to maintanance mode reply soon (6 Replies)
Discussion started by: knl.sundeep
6 Replies

7. AIX

What is the cause of USR filesystem full

we are using aix 5.3 and we notice that the filesystem /usr is almost full. we have an oracle database running on the server.what are the cause why this filesystem is almost full.what should we do to free some space on this filesystem beside increase the size?thanks (4 Replies)
Discussion started by: paulexis
4 Replies

8. AIX

Does HACMP have bugs increasing filesystem or Logical volumes

Hello, Does HACMP have bugs ? I have version 5.4 on AIX 6.1 and when I try to increase filesystem space or logical volume partitions which are under HACMP VG it gives me error: # lsvg rootvg pr0oravg px0oravg pb0oravg pr0sapvg px0sapvg pb0sapvg pr1_pr2_vg pr2_px1_vg # #... (11 Replies)
Discussion started by: filosophizer
11 Replies

9. AIX

Problem in increasing filesystem

Hi Friends, I have a problem while increasing the fileystem. Actually the filesystem is 256 gb and i have to add another 256 gb.So i got a new lun(hdisk) with 256 gb. I added to the vg using the extendvg command. It was successfully added, and when i checked the free pp's in vg it was showing... (4 Replies)
Discussion started by: Mohamed Thamim
4 Replies

10. Hardware

Increasing the filesystem size

Hi Guys We have a VM machine, now I want to increase the size of the filesystem. We are running RHEL6 O/S. I have filesystem that is 500GB I want to increase that filesystem to 1.5 TB. The guy who manages the VM increased the size on the VM machine, now how do I make sure that the... (7 Replies)
Discussion started by: Phuti
7 Replies
vgcfgrestore(1M)														  vgcfgrestore(1M)

NAME
vgcfgrestore - display or restore LVM volume group configuration from backup file or kernel memory SYNOPSIS
vg_name vg_name old_pv_path] pv_path vg_conf_path vg_conf_path old_pv_path] pv_path pv_path Remarks cannot be performed if the volume group is activated in shared mode. cannot be performed on devices attached to activated volume groups. Prior to restoring a backup configuration to a disk, detach the physi- cal volume from the volume group using the command (see pvchange(1M)), or deactivate the volume group using the command (see vgchange(1M)). will refuse to restore a configuration to a physical volume with a block size different than the block size stored in the configuration backup file for that physical volume. DESCRIPTION
The command restores the LVM configuration data from a default option) or alternate option) configuration backup file, or from kernel mem- ory option), to the physical volume named by pv_path. Or, it displays the configuration data on standard output option). The configuration stored for one physical volume, old_pv_path, can be copied to another physical volume pv_path option). Options and Arguments recognizes the following options and arguments: pv_path The raw (character) device path name of a physical volume that is currently online. If the option is omitted, pv_path must specify a physical volume whose configuration is stored in the configura- tion backup file. Get configuration information from the alternate configuration backup file vg_conf_path. This option is applicable to input arguments belonging to volume groups version 1.0. Forcibly restore the LVM configuration data even if the physical volume has alternate block(s) allocated inside the user data area. This option should be used with extreme caution. User is advised to fix the problem because potential data corruption could occur. Get configuration information from LVM data structures in kernel memory. The volume group containing pv_path must be activated in order to use this option. List the configuration information saved in the specified configuration backup file. Get configuration information from the default configuration backup file: vg_name is the path name of the volume group. base_vg_name is the base name of vg_name. For example, if vg_name is specified as base_vg_name is Restore the configuration information saved for physical volume old_pv_path to physical volume pv_path. This option is useful when a physical volume's name has changed since the configuration backup file was created or updated. old_pv_path must be the path name of a physical volume whose configuration is stored in the configuration backup file. It needs not be currently online. pv_path must be the path name of a physical volume that is currently online. Its configuration needs not be stored in the configuration backup file. Forcibly restore the LVM configuration data even if there is a physical volume mismatch between the kernel and the configuration backup file with the volume group still active. This option should not be used unless the configuration file is absolutely valid and up-to-date. Restoring invalid configuration data can result in data corruption later. If there are alternate physical volume links configured in the system, the following message will appear when total number of physical volumes in the kernel does not match with the configuration backup file due to missing alternate physical volume links: Mismatch between the backup file and the running kernel: Kernel indicates X disks for /dev/vgname; /etc/lvm- conf/vgname indicates Y disks. Cannot proceed with the restoration. Deactivate the Volume Group and try again. In this case, the user is advised to deactivate the volume group first, then use the command to restore configu- ration data when the volume group is unavailable. But if the volume group has to stay available and the user is absolutely sure the configuration file is correct, this option will restore data from the configuration file when the volume group stays available. Provide additional information when invoked together with option. o Additional values displayed for each path: o Disk size in kilobytes o Starting block number (kb) of the user data. o The PVkey (see Note that paths with the same key are links to the same device. Additional values displayed for each volume group: o max_pv o max_pe o max_lv o vg_version o vg_size (only volume groups version 2.0 or higher, see vgcreate(1M)) RETURN VALUE
exits with one of the following values: Successful completion. Failure. Errors occurred during the restore operation. 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
Restore the LVM configuration information for the physical volume that was saved in the default file Force to restore the LVM configuration data when volume group is still active: Restore the LVM configuration information to physical volume using alternate configuration file List backup information saved in default configuration file Above command might display the following: Restore LVM configuration information stored for in default configuration file to physical volume Restore LVM configuration information to physical volume using LVM data structures in kernel memory. The volume group containing must be activated: AUTHOR
was developed by HP. SEE ALSO
pvchange(1M), vgcfgbackup(1M), vgchange(1M), intro(7), lvm(7). vgcfgrestore(1M)
All times are GMT -4. The time now is 12:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy